FW: Bugs in Windows 2000 filesystem utilities?

From: Mark Medici (mark@DBMA.COM)
Date: 01/28/02 

Date:         Mon, 28 Jan 2002 11:12:55 -0500
From: Mark Medici <mark@DBMA.COM>
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM

One of the rules I've been taught to follow is to always match the NTFS format's disk allocation unit size to the stripe size on hardware RAID volumes. For example, if I configure my hardware RAID controller to use 64KB stripe size, then I would format the NTFS volume on that RAID array with the command "FORMAT x: /FS:NTFS /A:64K". And this always seemed to be good advice, particularly because empirical evidence demonstrates better performance with this configuration.

Unfortunately, Windows 2000 seems to not allow three important features to be used on NTFS volumes formatted with non-default allocation unit sizes: defragmentation, file/folder compression and file/folder encryption. At least this is what I've encountered recently.

Is this a bug or a "feature"??? Are there any workarounds or patches to allow compression, encryption and defragmentation of NTFS volumes configured for larger allocation unit sizes (for better performance)???

Thanks.

oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Delivery co-sponsored by VeriSign - The Internet Trust Company
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
FREE E-COMMERCE SECURITY INFRASTRUCTURE GUIDE
When building an e-commerce site, you want to start with a strong, secure
foundation. Learn how with VeriSign's FREE White Paper, "Building an
E-Commerce Trust Infrastructure." See how you can authenticate your site to
customers, use 128-Bit SSL encryption to secure your web servers, and accept
secure payments online. Click here:
http://www.verisign.com/cgi-bin/go.cgi?a=n116965650045000
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

Relevant Pages