garycahn
asked on
Macintosh Name space not working properly
On a Netware 3.12 system, I recently added Macintosh name space. Before I did this, I could go a year or more without having to run Vrepair. Now I have to run vrepair every week to correct hundreds of errors that are occurring on my network.
When I run vrepair, I get a long list of errors, which I have reprinted below. They all follow one of a couple of patterns. They either say that "Name was not properly zero padded." Or they say, "Macintosh file entry invalid name."
Interestingly, we don't even have a Macintosh computer on our network, so the problem is occurring as a result of windows computers---not Macs.
I have checked the novell site to make sure that I have the newest version of the Mac name space. I do. It is dated 9/26/1995
Why are these errors occurring, and what can I do to prevent them?
Here's the full text of some of the errors:
Error at file entry 45937
Original Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
Corrected Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
/*************************
Error at file entry 45949
Original Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
Corrected Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
/*************************
Error at file entry 53390
Original Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\ROADSH
Size: 0
Corrected Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\ROADSH
Size: 0
/*************************
Error at file entry 91405
Original Entry - Deleted Macintosh file entry
Name: \DATA\GROUP\COMCARE\ACN-TE
Size: 0
Name was not properly zero padded
Corrected Entry - Deleted Macintosh file entry
Name: \DATA\GROUP\COMCARE\ACN-TE
Size: 0
/*************************
Error at file entry 118740
Original Entry - Deleted Macintosh file entry
Name: \DATA\DAVID\PRIMEDIA\VR000
Size: 0
Name was not properly zero padded
Corrected Entry - Deleted Macintosh file entry
Name: \DATA\DAVID\PRIMEDIA\VR000
Size: 0
/****************
When I run vrepair, I get a long list of errors, which I have reprinted below. They all follow one of a couple of patterns. They either say that "Name was not properly zero padded." Or they say, "Macintosh file entry invalid name."
Interestingly, we don't even have a Macintosh computer on our network, so the problem is occurring as a result of windows computers---not Macs.
I have checked the novell site to make sure that I have the newest version of the Mac name space. I do. It is dated 9/26/1995
Why are these errors occurring, and what can I do to prevent them?
Here's the full text of some of the errors:
Error at file entry 45937
Original Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
Corrected Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
/*************************
Error at file entry 45949
Original Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
Corrected Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\STATEW
Size: 0
/*************************
Error at file entry 53390
Original Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\ROADSH
Size: 0
Corrected Entry - Macintosh file entry
Name: \DATA\GROUP\COMCARE\ROADSH
Size: 0
/*************************
Error at file entry 91405
Original Entry - Deleted Macintosh file entry
Name: \DATA\GROUP\COMCARE\ACN-TE
Size: 0
Name was not properly zero padded
Corrected Entry - Deleted Macintosh file entry
Name: \DATA\GROUP\COMCARE\ACN-TE
Size: 0
/*************************
Error at file entry 118740
Original Entry - Deleted Macintosh file entry
Name: \DATA\DAVID\PRIMEDIA\VR000
Size: 0
Name was not properly zero padded
Corrected Entry - Deleted Macintosh file entry
Name: \DATA\DAVID\PRIMEDIA\VR000
Size: 0
/****************
If you don't have Mac on your network, why did you add the name space?
ASKER
I had a Mac on the network for 2 days, and then took it off. I removed it 2 months ago, but these errors have continued to occur.
Frankly, I would like to delete the Mac name space altogether, but when I tried that using Vrepair, I got another series of errors that occurred on each and every directory on the network. Since all those errors occurred, I stopped the process midway, and just left the Mac Name space the way it was.
Frankly, I would like to delete the Mac name space altogether, but when I tried that using Vrepair, I got another series of errors that occurred on each and every directory on the network. Since all those errors occurred, I stopped the process midway, and just left the Mac Name space the way it was.
You need to remove the MAC name space. Purge all deleted files first.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your 2 suggestions. Regarding the download from Novell. I got it, but the files it contains have the same dates as what I already have on my network.
Regarding the idea of deleting the namespace. As I mentioned above, I began that process.
I got errors for every single directory on my server. I've reprinted the errors below. The odd thing was that even though I was deleting the mac name space, the error was an OS2 directory error. In any case, since I was getting the error on every single directory, I decided to abort the deletion of the name space. I am reluctant to try deleting the name space, until I understand what was causing all those errors, given that it is my Sys volume, and I don't want to end up with a a volume that I can't mount.
Error at entry 22
Original Entry - OS2 directory entry
Name: \LOGIN
The name space list is invalid
Corrected Entry - OS2 directory entry
Name: \LOGIN
/*************************
Error at entry 23
Original Entry - OS2 directory entry
Name: \SYSTEM
The name space list is invalid
Corrected Entry - OS2 directory entry
Name: \SYSTEM
/*************************
Error at entry 24
Original Entry - OS2 directory entry
Name: \PUBLIC
The name space list is invalid
Corrected Entry - OS2 directory entry
Name: \PUBLIC
Regarding the idea of deleting the namespace. As I mentioned above, I began that process.
I got errors for every single directory on my server. I've reprinted the errors below. The odd thing was that even though I was deleting the mac name space, the error was an OS2 directory error. In any case, since I was getting the error on every single directory, I decided to abort the deletion of the name space. I am reluctant to try deleting the name space, until I understand what was causing all those errors, given that it is my Sys volume, and I don't want to end up with a a volume that I can't mount.
Error at entry 22
Original Entry - OS2 directory entry
Name: \LOGIN
The name space list is invalid
Corrected Entry - OS2 directory entry
Name: \LOGIN
/*************************
Error at entry 23
Original Entry - OS2 directory entry
Name: \SYSTEM
The name space list is invalid
Corrected Entry - OS2 directory entry
Name: \SYSTEM
/*************************
Error at entry 24
Original Entry - OS2 directory entry
Name: \PUBLIC
The name space list is invalid
Corrected Entry - OS2 directory entry
Name: \PUBLIC
garycahn:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:
Accept: geoffryn {http:#6270213}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
ShineOn
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
Accept: geoffryn {http:#6270213}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
ShineOn
EE Cleanup Volunteer