Default Allocation Unit Size for NTFS Format?

  • Thread starter Thread starter Jisha
  • Start date Start date
J

Jisha

When using "Disk Management" to format a partition w/ NTFS, there are three
options concerning the allocation unit size:

1) Default
2) 512
3) 1024

What is the "Default" allocation unit size?
 
Greetings --

4 Kb (4096 bytes)

Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Thanks Bruce...

Since the options for allocation unit sizes are not identified as either
bytes or Kbytes... I presume the default of 4096 is 4 times the size of the
1024 option... correct?

Also, how can I verify the Allocation unit size for any given NTFS partition
(using w2kpro or other utility?)

Chris
 
Greetings --

Correct.

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.

Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Thanks again, Bruce :)

Unfortunately, those didn't work on w2Kpro...
I searched around for something similar, but couldn't find anything, ...

Chris
 
Jisha,

You are so lucky...
I mean to have met Bruce for your questions.
He is a very caring very knowledgeable individual.
I have learned much from him.

Thanks Bruce

:-)
don
--------------


Thanks again, Bruce :)

Unfortunately, those didn't work on w2Kpro...
I searched around for something similar, but couldn't find anything, ...

Chris
 
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

F:\>fsutil /?
'fsutil' is not recognized as an internal or external command,
operable program or batch file.

F:\>
 
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 : 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" <[email protected]>
: > Wrote in message : >
: > <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.

: > : > >
: > > <SNIP>
: > > Also, how can I verify the Allocation unit size for any given NTFS partition
: > > (using w2kpro or other utility?)
 
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.
---------------------------------
 
Hi Christopher,

Try using the following command "to obtain an accurate reporting (see**) for C:
alone." Note: The command is CPU and time intensive.

dir c:\ /s

According to the following Microsoft Knowledge Base Article: "this command traverses
the Junction/Mount points and provides accurate statistics for the drive C
namespace."

KB197000 - Disk Space Reporting Does Not Include Junction Point Targets
http://support.microsoft.com/?scid=197000

--
Carrie Garth, Microsoft MVP for Windows 2000
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- c x g

: "Jisha" <jisha AT hamptons DOT com>
: Wrote in message : Sent: Monday, October 06, 2003 01:37 PM
: <SNIP>
: I presume reluctantly that ALL NTFS folder-mountings from C: must first be
: removed to obtain an accurate reporting (see**) for C: alone... correct?
: <SNIP>

: > "Carrie Garth (MVP)"
: > Wrote in message : > Sent: Monday, October 06, 2003 01:37 PM
: > <SNIP> read-only chkdsk command <SNIP>
: > (dfrg.msc) to analyze the volume then view the resulting report.
: > <SNIP> http://support.microsoft.com/?scid=303079 <SNIP>

: > : "Jisha" <jisha AT hamptons DOT com>
: > : Wrote in message : > : 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" <[email protected]>
: > : > Wrote in message : > : >
: > : > <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
: > : > : > : > >
: > : > > <SNIP>
: > : > > Also, how can I verify the Allocation unit size for any given NTFS
: > : > > partition (using w2kpro or other utility?)
 
Hello Carry...

Thank you for the suggestion and the KB URL.
....and your previous suggestions.

yes... the "dir c:\ /s" will give me statistics for the C: partition and all
partitions mounted from there...

But, I was actually trying to go the other way around; to get statistics for
C: alone... ;_((
....excluding any mount-points.

Actually, since my previous post, I realized I CAN use the procedure
described in KB303079 - How to Locate and Correct Disk Space Problems on
NTFS Volumes
http://support.microsoft.com/?scid=303079 .

Instead of removing all of the mount-points from the drive... I just removed
the drive from the mount-points!
You see, I keep all HDD's in removable/heat-sink/cooling cartridges.
I just pulled the cartridge and stuck it into a different computer...Voila!

Who says genius requires high I.Q. ! ;-))

Christopher
 
Back
Top