drodey
asked on
Dir sizes in Netware 4.11
I'm trying to get an accurate listing of the size any particular dir (and all it's subdir's) take on a NW 4.11 server. Running NT 4.0 w/ SP4, NT Explorer gives me whacky numbers (in the TB range!) when I only have 12 GB max space. Winfile is useless. Opening a DOS prompt and running 'dir /s/e' doesn't seem to give me accurate numbers either. I tried NWADMIN & FILER. They dont provide that info either. Any other accurate utility? I get accurate size on some dir's but not on others. It seems like I exceed some allowable limit (too many total files/subdirs?).
ASKER
brosenb0,
Actually, the command is 'NDIR /SUB' but I was actually looking for a more GUI approach. Doing it from dos using NDIR is too lengthy...
Regardless, I found some utility at a site that has a bunch of little useful Novell utilities. It's called SHOWSIZE.
Thanks anyway!
Actually, the command is 'NDIR /SUB' but I was actually looking for a more GUI approach. Doing it from dos using NDIR is too lengthy...
Regardless, I found some utility at a site that has a bunch of little useful Novell utilities. It's called SHOWSIZE.
Thanks anyway!
How about sharing the address of that site w/ us?
You must have an old version of NDIR.Exe. Mine works recurses sub-dirs fine with the /S switch. If you want to speed up NDIR, use the /SORT UN switch to stop it sorting the files in each directory.
I believe the inaccuracy in sizes comes from the fact that you have activated the option of compressing files not beeing used.
NwAdmin is Novell's utility for this purpose. You select the volume and you click on properties. This shows you numbers graphs etc.
Thanks,
Yiannis
NwAdmin is Novell's utility for this purpose. You select the volume and you click on properties. This shows you numbers graphs etc.
Thanks,
Yiannis
ASKER
anadrash, No compression is enabled anywhere.
westone, Sure, the web site is http://www.net-utils.com/
brosenb0, I'll confirm my NDIR date/time is up to date.
Thanks to all for your help!
westone, Sure, the web site is http://www.net-utils.com/
brosenb0, I'll confirm my NDIR date/time is up to date.
Thanks to all for your help!
"No compression is enabled anywhere" - do you run your server without compression?
Why?
Saar.
Why?
Saar.
ASKER
saar2,
Yes. No volumes have compression enabled. Why? I'd rather not introduce additional variables on production servers that cant afford downtime and that already have sufficient hdd space w/o compression enabled. Additionally, I dont trust compression based on the problem reports i've read from Novell...
Yes. No volumes have compression enabled. Why? I'd rather not introduce additional variables on production servers that cant afford downtime and that already have sufficient hdd space w/o compression enabled. Additionally, I dont trust compression based on the problem reports i've read from Novell...
Is this question completed ?
it may be an idea to track down if the 'huge sizes' are everywhere... (even in empty directories that you create, and that are no subdirectories). If only certain directories have the problem then 'idea 1'. If not, 'idea 2'.
idea 1:
Any chance, you have some 'sparse' files in the directory structure?
A database and other applications can 'goof' and write a file in a way that Netware will cause a 'sparse' file. If you look at the file directory, you will see a file that is huge. (say 2 gig) in size. For example, I use a database application that handles 1K records. I have it write record 1, and then, have it write record 1million. Well, Netware will create a 'sparse' file... which will be 1GIG in size, but, actually only consume about a MEG on the drive.
idea 2:
The dsk drive is incorrect for the drive that you have. Its close enough to maintain data integrity but the 'number of cylinders' (or other geometry) is wrong, so, the various utilities can not calculate a correct size.
My bet is on idea 1. good luck
idea 1:
Any chance, you have some 'sparse' files in the directory structure?
A database and other applications can 'goof' and write a file in a way that Netware will cause a 'sparse' file. If you look at the file directory, you will see a file that is huge. (say 2 gig) in size. For example, I use a database application that handles 1K records. I have it write record 1, and then, have it write record 1million. Well, Netware will create a 'sparse' file... which will be 1GIG in size, but, actually only consume about a MEG on the drive.
idea 2:
The dsk drive is incorrect for the drive that you have. Its close enough to maintain data integrity but the 'number of cylinders' (or other geometry) is wrong, so, the various utilities can not calculate a correct size.
My bet is on idea 1. good luck
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Run NDIR /S (subdirectories) or NDIR /S /C (continuous) and it will give you the total files, directories and total file size at the end of its listing. It will also tell you how much actual disk space the files used, based on the allocation unit size.