Thanks very much Carrie...
Your reply was very helpful. I was able to verifiy the 'allocation unit
size' in use on various partitions of concern.
....embarrassing as it may be... as in hindsight, I should have been able to
figure this out myself !
BUT...
I read KB 303079 carefully, and have just 1 question... which I probably
already know the answer to, but don't want to face it!
I presume reluctantly that ALL NTFS folder-mountings from C: must first be
removed to obtain an accurate reporting (see**) for C: alone... correct?
** Following the procedure described in "Excerpt 'A' " below, and in light
of "Excerpt 'B' " below, the following data was reported for my system
partition (c

, which was created to be (as close as possible to) exactly
20.00 GB (1024x20mb):
Size: 19.4 GB
Size on disk: 19.5 GB
However, there are several hundreds of GBs on separate drives and
partitions, all NTFS folder-mounted from C: .
As the procedure was calculating its results, I saw that ALL drives and
partitions were accessed and presumably included in the above result.
Clearly, the reported sizes are incorrect... as
1) "Size on disk" is not ? "Size", and is seriously under-reported (?),
....and
2) Excerpt "B" below.
---------------------------------
Excerpt "A" From: 303079 - How to Locate and Correct Disk Space Problems on
NTFS Volumes:
To see if this is the optimal cluster size, determine the amount of wasted
space by following these steps:
Double-click My Computer on the desktop, and then double-click the drive
letter (for example, D) of the volume in question.
This opens the volume and displays folders and files contained in the root.
1. Click any file or folder, and then click the Select All option on the
Edit menu.
2. With all files and folders selected, right-click any file or folder, and
then click the Properties option.
This opens a Properties dialog box that contains a General tab. It also
tabulates the total number of files and directories on the entire volume and
provides two file size statistics: SIZE and SIZE ON DISK.
3. With all files and folders selected, right-click any file or folder, and
then click the Properties option.
This opens a Properties dialog box that contains a General tab. It also
tabulates the total number of files and directories on the entire volume and
provides two file size statistics: SIZE and SIZE ON DISK.
If you are not using NTFS compression for any files or folders contained on
the volume, the difference between SIZE andSIZE ON DISK is wasted space
because of a larger-than-necessary cluster size.
---------------------------------
Excerpt "B" From: 303079 - How to Locate and Correct Disk Space Problems on
NTFS Volumes:
Volume mount points and directory junctions allow an empty folder on an NTFS
volume to point to the root or subfolder on another volume. Windows Explorer
and a DIR /s command follow the reparse point, count any files and
directories on the destination volume, and include them in the host volume's
statistics. This may lead you to believe that more space is being used on
the host volume than what is actually being used.
---------------------------------
"Carrie Garth (MVP)" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Chris,
>
> In Windows 2000 you can determine the cluster size by running a read-only
chkdsk
> command from a command prompt. Alternatively, you can use the built-in
Disk
> Defragmenter (dfrg.msc) to analyze the volume then view the resulting
report. For
> more information see the following Microsoft Knowledge Base Article:
>
> KB303079 - How to Locate and Correct Disk Space Problems on NTFS Volumes
> http://support.microsoft.com/?scid=303079
>
> BTW, fsutil is not a built-in Windows 2000 program. However, according to
KB176970
> you can use it on a Windows 2000 computer after you "Copy FSUtil.exe from
the
> %SystemRoot%\System32 folder on a Windows XP-or-later-based computer to
the local
> drive on the Windows 2000-based computer."
>
> KB176970 - How to Run the CHKDSK /F Command on a Shared Cluster Disk
> http://support.microsoft.com/?scid=176970
>
> --
> Carrie Garth, Microsoft MVP for Windows 2000
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- c x g
>
> : "Jisha" <jisha AT hamptons DOT com>
> : Wrote in message news:%(E-Mail Removed)
> : Sent: Saturday, October 04, 2003 05:27 PM
> :
> : <SNIP> Unfortunately, those didn't work on w2Kpro...
> : I searched around for something similar, but couldn't find anything, ...
>
> : > "Bruce Chambers" <(E-Mail Removed)>
> : > Wrote in message news:(E-Mail Removed)
> : >
> : > <SNIP>
> : > I don't have a Win2K machine handy to test this, but, on WinXP
> : > Pro, the command fsutil fsinfo ntfsinfo c: run from the command prompt
> : > would reveal that info.
>
> : > > "Jisha" <jisha AT hamptons DOT com> wrote in message
> : > news:(E-Mail Removed)...
> : > >
> : > > <SNIP>
> : > > Also, how can I verify the Allocation unit size for any given NTFS
partition
> : > > (using w2kpro or other utility?)
>
>
>