I recently took over a small hospital network (one Novell 4.11 server and one SCO Unix, 70 win95 workstations, 3 win98) This week we observed apparent directory corruption with some very localized data loss (one app.) The corruption manifests in windows explorer where folder capacity is shown much, much smaller than the "bytes used." For example, in one of the data loss folders the capacity is shown as 32K with ~260K bytes used. The directory was zipped and sent to the app vendor where the same size discrepancy was observed. One other strange point - if I look at the folders through Network Neighborhood the capacity information appears correct but the data loss is still there. I have restarted the server and run vrepair (but not yet dsrepair.) The latest McAfee set does not find a virus. Ideas? Thanks for your help.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Directory corruption problem
- Thread starter Jim01
- Start date
Ok, here's what I would recommend doing:
Do a LOAD DSREPAIR -RC this will make a backup of the NDS Database since you only have one server. 2. Copy the repair file off the server to your local PC, in case the server crashes hard, you want to have access to this folder, go to and do a search on the DSREPAIR -RC and it will tell you the name of the backup file. Make sure you have a good backup of the Data as well. You may want to verify this via your tape backup software. Finally, LOAD DSREPAIR -A, Select Advaned Options, Repair Local Database. Run this a couple times until you see that the number of errors = 0, when complete, save the database (you need to save the database after each concurrent repair) then look to see what is being reported etc. If the error still exists, then chances are the file(s) have become corrupted and it is not an NDS error. You may want to familiarize yourself with DSREPAIR if you have not already as well as running this repair monthly. There are also TIDs on performance tuning a Netware server. Good thing to review since most servers can be tweaked nicely.
HTH
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
Do a LOAD DSREPAIR -RC this will make a backup of the NDS Database since you only have one server. 2. Copy the repair file off the server to your local PC, in case the server crashes hard, you want to have access to this folder, go to and do a search on the DSREPAIR -RC and it will tell you the name of the backup file. Make sure you have a good backup of the Data as well. You may want to verify this via your tape backup software. Finally, LOAD DSREPAIR -A, Select Advaned Options, Repair Local Database. Run this a couple times until you see that the number of errors = 0, when complete, save the database (you need to save the database after each concurrent repair) then look to see what is being reported etc. If the error still exists, then chances are the file(s) have become corrupted and it is not an NDS error. You may want to familiarize yourself with DSREPAIR if you have not already as well as running this repair monthly. There are also TIDs on performance tuning a Netware server. Good thing to review since most servers can be tweaked nicely.
HTH
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
- Status
Similar threads
- Locked
- Question
- Locked
- Question