Microsoft takes wraps off new Windows file system

Microsoft takes wraps off new Windows file system

Summary: The Resilient File System or ReFS, the successor to NTFS, will make its first appearance in Windows Server 8, after which Microsoft will introduce it for client storage and ultimately boot volumes

SHARE:
TOPICS: Windows, Networking
4

Microsoft has given its first detailed description of ReFS, the new file system that will gradually succeed the now-venerable NTFS in Windows systems.

Windows 8 Server preview

The Resilient File System or ReFS, the successor to NTFS, will make its first appearance in Windows Server 8.

The Resilient File System (ReFS) will make its first appearance as a storage system in Windows Server 8, after which it will evolve into a system for client storage, then ultimately for boot volumes. On Monday, Microsoft used a post on its Building Windows 8 blog to lay out details on ReFS.

"Along with Storage Spaces, ReFS forms the foundation of storage on Windows for the next decade or more," Microsoft development manager Surendra Verma wrote. "We believe this significantly advances our state of the art for storage... we expect that we will see ReFS as the next massively deployed file system."

The "staged evolution" of ReFS, beginning with its use as a file server, is the same approach Microsoft has taken with previous file systems.

According to Verma, ReFS has many of the same features and semantics as NTFS, which was introduced in 1993. These include "BitLocker encryption, access-control lists for security, USN journal, change notifications, symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs and OpLocks".

If a file-access API can access an NTFS volume, it will be able to access data stored on ReFS.

"Rewriting the code that implements file system semantics would not lead to the right level of compatibility, and the issues introduced would be highly dependent on application code, call timing and hardware. Therefore in building ReFS, we reused the code responsible for implementing the Windows file system semantics," Verma said.

On-disk storage engine

What has changed is the on-disk storage engine underneath the reused code. The ReFS engine exclusively uses the so-called B+ tree structure to represent stored information. Verma indicated this will mean a simpler system, with the choice of structure designed to be as scalable as possible.

Along with Storage Spaces, ReFS forms the foundation of storage on Windows for the next decade or more.

– Surendra Verma, Microsoft

On the subject of detecting and fixing corruption, Verma explained that all ReFS data is check-summed at the level of the B+ tree page, with the checksum — an algorithm for checking data integrity — being stored away from that page.

"This allows us to detect all forms of disk corruption, including lost and misdirected writes and bit rot (degradation of data on the media). In addition, we have added an option where the contents of a file are check-summed as well," Verma wrote. 

The Storage Spaces feature will be available for NTFS and, unlike ReFS, for client PCs from the start. It is supposed to improve performance and protect data by maintaining copies on multiple disks.

When ReFS is used alongside mirrored Storage Spaces, corruptions will be "automatically and transparently fixed", Verma added, noting that ReFS also had a 'salvage' feature for making sure that non-repairable corruption does not affect the availability of "good data".

Scrubbing

ReFS offers a new way of dealing with 'bit rot', or data decay, in that it uses a system task to "periodically [scrub] all metadata and Integrity Stream data on a ReFS volume residing on a mirrored Storage Space", Verma said.

"Scrubbing involves reading all the redundant copies and validating their correctness using the ReFS checksums. If checksums mismatch, bad copies are fixed using good ones," he said, adding that "the file attribute FILE_ATTRIBUTE_NO_SCRUB_DATA indicates that the scrubber should skip the file".

Responding to readers' questions about the blogpost, Verma also stressed that Windows 7 users would be able to read ReFS-formatted partitions from a Windows 8 Server, either by using a new file system driver or by sharing a folder out from the server.

"Note that support for NTFS is going to be present in Windows for the foreseeable future, so you should always be able to access all your NTFS data across versions without any problems," he added.


Get the latest technology news and analysis, blogs and reviews delivered directly to your inbox with ZDNet UK's newsletters.

Topics: Windows, Networking

David Meyer

About David Meyer

David Meyer is a freelance technology journalist. He fell into journalism when he realised his musical career wouldn't pay the bills. David's main focus is on communications, as well as internet technologies, regulation and mobile devices.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

4 comments
Log in or register to join the discussion
  • "Along with Storage Spaces, ReFS forms the foundation of storage on Windows for the next decade or more,"...

    Microsoft shouldn't be wasting its time on technology for the ten-year term; it needs to devote ALL its resources to relevance and survival on a year-to-year basis.

    Warmest regards...
    bakerdriver
  • Above should read

    "...on a quarterly basis...".


    Warmest regards...
    bakerdriver
  • I am more interested to see if they address stability issues. I'm not surprised to see Microsoft try to improve NTFS. It's simply not a stable filesystem. Countless times on servers, we've had cases of disappearing files, as well as disappearing permissions and ownership. And on many other occasions, NTFS becomes corrupted on clients which can result in data loss. Yes, I know, backups are how we can prevent data loss. But on every client it would be a huge undertaking and even though we try to force users to store on network drives that are backed up, they still find ways to retain local files. But should the filesystem fail? I've been using open source filesystems like ext2, ext3, and ext4 on GNU/Linux, and have never witnessed the same type of corruption that NTFS has on known good hardware.
    Chris_Clay
  • Sounds a bit like ZFS to me... Well done MS for catching up.

    Unix wins :P
    huggy79