Building the next generation file system for Windows: ReFS
Quote:
•Maintain a high degree of compatibility with a subset of NTFS features that are widely adopted while deprecating others that provide limited value at the cost of system complexity and footprint.
•Verify and auto-correct data. Data can get corrupted due to a number of reasons and therefore must be verified and, when possible, corrected automatically. Metadata must not be written in place to avoid the possibility of "torn writes," which we will talk about in more detail below.
•Optimize for extreme scale. Use scalable structures for everything. Don't assume that disk-checking algorithms, in particular, can scale to the size of the entire file system.
•Never take the file system offline. Assume that in the event of corruptions, it is advantageous to isolate the fault while allowing access to the rest of the volume. This is done while salvaging the maximum amount of data possible, all done live.
•Provide a full end-to-end resiliency architecture when used in conjunction with the Storage Spaces feature, which was co-designed and built in conjunction with ReFS.
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 (also known as copy on write)
•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
Source: Windows 8 Blog
http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-next-generation-file-system-for-windows-refs.aspx
Quote:
The key goals of ReFS are:
•Maintain a high degree of compatibility with a subset of NTFS features that are widely adopted while deprecating others that provide limited value at the cost of system complexity and footprint.
•Verify and auto-correct data. Data can get corrupted due to a number of reasons and therefore must be verified and, when possible, corrected automatically. Metadata must not be written in place to avoid the possibility of "torn writes," which we will talk about in more detail below.
•Optimize for extreme scale. Use scalable structures for everything. Don't assume that disk-checking algorithms, in particular, can scale to the size of the entire file system.
•Never take the file system offline. Assume that in the event of corruptions, it is advantageous to isolate the fault while allowing access to the rest of the volume. This is done while salvaging the maximum amount of data possible, all done live.
•Provide a full end-to-end resiliency architecture when used in conjunction with the Storage Spaces feature, which was co-designed and built in conjunction with ReFS.
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 (also known as copy on write)
•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
Source: Windows 8 Blog
http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-next-generation-file-system-for-windows-refs.aspx
