Claus Joergensen, one of the founding fathers of windows Storage server, had a great post today about a new white paper, available here, discussing the best practices and guidance for sizing ntfs volumes. The paper also has details on self-healing NTFS and Chkdsk execution times on Windows server 2008 R2.
When planning Windows file server deployments, we are often asked questions such as “How large can I make my volumes?” or “How long will it take to repair a volume?”. This white paper helps answer these questions.
Table of Contents:
- Self-Healing and Chkdsk
- How to run Chkdsk
- Chkdsk Exit Codes
- Improving General Availability of the Server
- Chkdsk performance on Windows Server 2008 r2
- Block Caching Improvements in Windows server 2008 r2
- Effect of Volume Size on execution time of Chkdsk
- Effect of Number of files and Different OS versions on execution time of Chkdsk
- Effect of Physical Memory at different Number of files on execution time
- Effect of short file names on Chkdsk execution time
- Effect of Enabling/Disabling short file names
- Call to Action
If you are planning a Windows file server deployment or is looking to upgrade an existing Windows file server deployment to Windows Server 2008 R2, you should consult the white paper. It outlines how with Windows Server 2008 R2, NTFS can scale to easily support 15 TB file systems with 10 million files! Even with hundreds of millions of files the Chkdsk execution times are really fast. My favorite statistic is that a volume with 300 million files is able to Chkdsk in about 6 hours, that is so much faster than the old days.