W
Will
What is the impact of having a RAID system stripe data at a size
that is a multiple larger than the Windows 2000 file allocation
unit size? Windows 2000 apparently doesn't like to have
allocation units larger than 4K. When I tried doing this, I
found out that defragmentation tools stopped working, my backup
program Backup Exec 10.0 would randomly hang while reading or
writing a large disk, and Windows 2000's boot sector would be
trashed on every reboot of the machine.
I'm therefore "stuck" with the standard Windows 2000 4K file
allocation unit for NTFS file systems. But the RAID system I am
building that NTFS volume on has a stripe size that goes from 8K
to 128K. I cannot select 4K. What are the implications of
having the stripe be larger than the NTFS allocation unit?
As a note, my application for this volume requires reading huge
numbers of 42K files rapidly in sequence.
that is a multiple larger than the Windows 2000 file allocation
unit size? Windows 2000 apparently doesn't like to have
allocation units larger than 4K. When I tried doing this, I
found out that defragmentation tools stopped working, my backup
program Backup Exec 10.0 would randomly hang while reading or
writing a large disk, and Windows 2000's boot sector would be
trashed on every reboot of the machine.
I'm therefore "stuck" with the standard Windows 2000 4K file
allocation unit for NTFS file systems. But the RAID system I am
building that NTFS volume on has a stripe size that goes from 8K
to 128K. I cannot select 4K. What are the implications of
having the stripe be larger than the NTFS allocation unit?
As a note, my application for this volume requires reading huge
numbers of 42K files rapidly in sequence.