In this blog post I’d like to talk about a new file system for Windows. This file system, which Microsoft calls ReFS (Resilient File System), has been designed from the ground up to meet a broad set of customer requirements, both today’s and tomorrow’s, for all the different ways that Windows is deployed. Although it is designed to be better in many dimensions, resiliency stands out as one of its most prominent features.
NTFS, the New Technology File System, first shipped on Windows NT 3.1 when it was introduced in 1995 but didn’t make its way to the desktop until Microsoft retired the Windows 9x code and shipped Windows XP in 2001.
The key features of ReFS are as follows (note that some of these features are provided in conjunction with Storage Spaces).
– Metadata integrity with checksums
– Integrity streams providing optional user data integrity
– Allocate on write transactional model for robust disk updates
– Large volume, file and directory sizes
– Storage pooling and virtualization makes file system creation and management easy
– Data striping for performance (bandwidth can be managed) and redundancy for fault tolerance
– Disk scrubbing for protection against latent disk errors
– Resiliency to corruptions with “salvage” for maximum volume availability in all cases
– Shared storage pools across machines for additional failure tolerance and load balancing
Windows 8 client is able to access and read ReFS volumes until it’s fully supported in client operating systems in the future, but now:
– You can not convert data between NTFS and ReFS
– You can not boot from ReFS in Windows Server 2102
– ReFS can not be used on removable media or drives
– The NTFS features not supported in ReFS are: named streams, object IDs, short names, compression, file level encryption (EFS), user data transactions, sparse, hard-links, extended attributes, and quotas.
To learn more about ReFS file system, click here.