Hello
i wanted to check the default allocation unit size of c (an raid 10 array created from 512b logical and physical sector disks and ashift = 9)
and d (an raid 10 array created from 512b logical 4096b physical sector disks adn ashit =12) so I run (inside windows in cli) command
fsutil fsinfo ntfsInfo C:
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
and for d afterwards fsutil fsinfo ntfsInfo D:
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
I suppose for c (since it was created by 512b logical/physical drives) is ok for Bytes Per Physical Sector option to be 512 but why it is the same value for D drive also which is an array of 4096b drives? Shouldnt it be Bytes Per Physical Sector : 4096 ?
Another weird thing is that the first attempt to discover the allocation unit size was by creating a txt file in the c drive, typing few lines of characters, saving it and clicking properties afterwards to check the size on disk value. Well the size on disk was 0bytes while the above option real size (or file size) was 98bytes. Why is that?
PS In case it matters (which dont), the disk's option write cache is write back
The same behavior with 0 bytes is tested on all VMs with same zero value result
i wanted to check the default allocation unit size of c (an raid 10 array created from 512b logical and physical sector disks and ashift = 9)
and d (an raid 10 array created from 512b logical 4096b physical sector disks adn ashit =12) so I run (inside windows in cli) command
fsutil fsinfo ntfsInfo C:
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
and for d afterwards fsutil fsinfo ntfsInfo D:
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
I suppose for c (since it was created by 512b logical/physical drives) is ok for Bytes Per Physical Sector option to be 512 but why it is the same value for D drive also which is an array of 4096b drives? Shouldnt it be Bytes Per Physical Sector : 4096 ?
Another weird thing is that the first attempt to discover the allocation unit size was by creating a txt file in the c drive, typing few lines of characters, saving it and clicking properties afterwards to check the size on disk value. Well the size on disk was 0bytes while the above option real size (or file size) was 98bytes. Why is that?
PS In case it matters (which dont), the disk's option write cache is write back
The same behavior with 0 bytes is tested on all VMs with same zero value result
Last edited:
