Jump to content

ReFS

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by YoshiroShin (talk | contribs) at 01:32, 13 August 2015 (→‎Performance and competitor comparisons: Sentence improvment). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Not to be confused with ReiserFS.
ReFS
Developer(s)Microsoft
Full nameResilient File System
Introduced1 August 2012; 12 years ago (2012-08-01)[1] with Windows Server 2012
Limits
Max volume size1 yottabyte
Max file size16 exabytes
Features
AttributesYes
Transparent
compression		No
Copy-on-writeYes
Other
Supported
operating systems		Microsoft Windows
WebsiteResilient File System Overview

Resilient File System (ReFS),[2] codenamed "Protogon",[3] is a Microsoft proprietary file system introduced with Windows Server 2012 with the intent of becoming the "next generation" file system after NTFS.

ReFS was designed to overcome issues that had become significant over the years since NTFS was conceived, related to how data storage requirements had changed. Its key design advantages are intended to include — automatic integrity checking and data scrubbing, removing the need for chkdsk and protecting against data degradation; built-in handling of hard drive failure and redundancy, including RAID and a switch to copy/allocate on write for data and metadata updates; very long path and filename handling; and storage virtualization and pooling, including almost arbitrary logical volume size (as distinct from the physical sizes of the disks used).

These requirements arose from two major changes in storage systems and usage — the size of storage in use (large or massive arrays of multi-terabyte drives now being fairly common), and the need for continual reliability. As a result, the file system needs to be self-repairing (to prevent disk checking from being impractically slow or disruptive), along with abstraction or virtualization between physical disks and logical volumes.

ReFS was initially added to Windows Server 2012 only, with the aim of gradual migration to consumer systems in future versions (although modifications were quickly developed by enthusiasts for the latter). The initial versions removed some NTFS features, causing concern among onlookers, such as quota systems and extended attributes. Some of these were re-implemented in later versions of ReFS.

In its early versions (2012–2013), ReFS was similar or slightly faster than NTFS in most tests,[4] but far slower when full integrity checking was enabled, a result attributed to the relative newness of ReFS.[5][6] Concerns were also raised over Storage Spaces, the storage system designed to underpin ReFS, which is able to fail in a manner that prevents ReFS itself from recovering.[7][8][9]

Feature changes compared to NTFS

Major new features

Improved reliability for on-disk structures
ReFS uses B+ trees for all on-disk structures, including all metadata and file data.[10][11] Metadata and file data are organized into tables similar to a relational database. The file size, number of files in a folder, total volume size and number of folders in a volume are limited by 64-bit numbers; as a result, ReFS supports a maximum file size of 16 exabytes, a maximum of 18.4 × 1018 directories and a maximum volume size of 1 yottabyte (with 64 KB clusters) which allows large scalability with no practical limits on file and directory size (hardware restrictions still apply). Free space is counted by a hierarchical allocator which includes three separate tables for large, medium, and small chunks. Data scrubbing can be enabled optionally.[11]
Built-in resilience
ReFS employs an allocation-on-write update strategy for metadata,[10] which allocates new chunks for every update transaction and uses large IO batches. All ReFS metadata has built-in 64-bit checksums which are stored independently. The file data can have an optional checksum in a separate "integrity stream", in which case the file update strategy also implements allocation-on-write; this is controlled by a new "integrity" attribute applicable to both files and directories. If nevertheless file data or metadata becomes corrupt, the file can be deleted without taking down the whole volume offline for maintenance, then restored from the backup. As a result of built-in resiliency, administrators do not need to periodically run error-checking tools such as CHKDSK when using ReFS.
Compatibility with existing APIs and technologies
ReFS supports only a subset of NTFS features, and only Win32 APIs that are "widely adopted"; but does not require new system APIs and most file system filters continue to work with ReFS volumes.[10] ReFS supports many existing Windows and NTFS features such as BitLocker encryption, Access Control Lists, USN Journal, change notifications,[12] symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs, and oplock. ReFS seamlessly[10] integrates with Storage Spaces, a storage virtualization layer that allows data mirroring and striping, as well as sharing storage pools between machines.[13] ReFS resiliency features enhance the mirroring feature provided by Storage Spaces and can detect whether any mirrored copies of files become corrupt using background data scrubbing process, which periodically reads all mirror copies and verifies their checksums then replaces bad copies with good ones.

Removed features

Some NTFS features were removed and unsupported in the initial versions of ReFS. These included named streams, object IDs, 8.3 filename, NTFS compression, Encrypting File System (EFS), transactional NTFS, hard links, extended attributes, and disk quotas.[10][3] [14] ReFS does not itself offer data deduplication.[10] In addition, Windows cannot be booted from a ReFS volume.[10] Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces, however, automated error-correction is only supported on mirrored spaces.

In the subsequent implementation of ReFS in Windows 8.1 64-bit and Server 2012 R2, the file system reacquired alternate data streams and automatic correction of corruption when integrity streams are used on parity spaces.[15] ReFS had initially been unsuitable for Microsoft SQL Server instance allocation due to the absence of alternate data streams.[16]

As of March 2015, a review of the state of ReFS on WIndowsNetworking.com stated that:[17]

"You can’t (at least at this time) boot Windows from an ReFS volume and the first versions of ReFS don’t include file-level compression and encryption, disk quotas or hard links, all of which are advantages of NTFS over the FAT file systems. Note that ReFS does support sparse files, reparse points, case-sensitive file names and Unicode in file names and perhaps most important, it preserves and enforces access control lists (ACLs).
"It’s obvious that ReFS in its current iteration is not a replacement for NTFS ... because some applications that rely on specific NTFS features might not work with ReFS [... however...] Storage of most conventional data doesn’t require the specific NTFS features that aren’t supported by ReFS and so ReFS can handle that duty nicely. Its primary use case is on file servers that store extremely large amounts of data. It has data integrity and recovery mechanisms built into the file system, as well. That means those tools that are designed to detect and repair file corruption in other file systems aren’t necessary, so their incompatibility with ReFS isn’t really an issue. Additionally, although ReFS doesn’t support file level (Encrypting File System) encryption, BitLocker can be used to protect ReFS volumes so that’s not so much of an issue, either [...]
"ReFS has some distinct advantages over current reigning Windows file system NTFS, but it also has some drawbacks. It boasts self-healing powers, ability to repair files without down time, less risk that data will be lost when there’s a power failure (due to the way it writes metadata), and of course the ability to create huge volumes and files and even give those files names that are longer than 255 characters if you wish. But it’s not quite ready for prime time yet."

Stability and known issues

Issues identified or suggested for ReFS, when running on Storage Spaces (its intended design[9]), include:

  • Adding thin-provisioned ReFS on top of Storage Spaces (according to a 2012 pre-release article) can fail in a non-graceful manner, in which the volume without warning becomes inaccessible or unmanageable.[7] This can happen, for example, if the physical disks underlying a storage space becomes too full. Smallnetbuilder comments that, in such cases, recovery could be "prohibitive" as a "breakthrough in theory" is needed to identify storage space layouts and recover them, which is required before any ReFS recovery of file system contents can be started; therefore it recommends using backups as well.[7]
  • Even when Storage Spaces is not thinly provisioned, ReFS may still be unable to dependably correct all file errors in some situations, because Storage Spaces operates on blocks and not files, and therefore some files may potentially lack necessary blocks or recovery data if part of the storage space is not working correctly. As a result, disk and data addition and removal may be impaired, and redundancy conversion becomes difficult or impossible.[8]
  • Because ReFS was designed not to fail, if failure does occur, there are no tools provided to repair it. Third party tools are dependent on reverse engineering the system and (as of 2014) few of these exist.[9]

Performance and competitor comparisons

In 2014, a review of ReFS and assessment of its readiness for production use, concluded that ReFS had key advantages over two of its main file system competitors. ZFS (used in Solaris and FreeBSD, among others) was widely criticized for its comparatively extreme memory requirements of many gigabytes of RAM for online deduplication, which ruled it out from a large number of medium and smaller systems. However, turning off online deduplication on ZFS, as this feature is unsupported in ReFS, yields a more even comparison between the two file systems since ZFS then has a memory requirement of only a few hundred megabytes. Offerings such as Drobo used proprietary methods which have no fallback if the company behind them fails.[18]

ReFS was also found to be capable of running slightly faster than NTFS in most tests.[4] However, with integrity checking enabled, ReFS was found to be greatly slowed, and to run "dismally", suffering "a huge hit on performance and very high latency"; benchmark testing shows around 90% slowdown.[5][6] However, they also point out that ReFS is still very much a newcomer ("essentially a “1.0” feature that is rough around the edges") and has not had the time to reach maturity that file systems such as ZFS have had.[6]

In 2012, Phoronix wrote an analysis[19] of ReFS vs Btrfs, an experimental copy-on-write filesystem for Linux. Their features are similar, with both supporting checksums, RAID-like use of multiple disks, and error detection/correction. However, ReFS lacks deduplication, copy-on-write snapshots, and compression, all found in Btrfs and ZFS.

See also

References

  1. ^ Snover, Jeffrey (1 August 2012). "Windows Server 2012 released to manufacturing!". Windows Server Blog. Microsoft Corporation. Retrieved 2 September 2014.
  2. ^ Lucas, Martin (1 January 2013). "Windows Server 2012: Does ReFS replace NTFS? When should I use it?". Ask Premier Field Engineering (PFE) Platforms. Microsoft. TechNet blogs. Retrieved 20 January 2013.
  3. ^ a b Foley, Mary Jo (16 January 2012). "Microsoft goes public with plans for its new Windows 8 file system". ZDNet. CBS Interactive. Retrieved 21 January 2013.
  4. ^ a b http://www.firstever.eu/en/refs-vs-ntfs-benchmark/
  5. ^ a b http://bariseris.wordpress.com/2012/10/22/relative-performance-of-parity-vs-mirror-in-storage-spaces/
  6. ^ a b c http://jasoneckert.triosdevblog01.ca/blog/Entries/2014/2/25_Microsoft_ReFS_vs_Oracle_ZFS_-_FIGHT.html
  7. ^ a b c Elena Pakhomova of ReclaiMe.com (2012-Aug-08, BEFORE the release of Win8!) http://www.smallnetbuilder.com/nas/nas-features/31836-data-recovery-tales-when-windows-storage-spaces-go-bad
  8. ^ a b http://helgeklein.com/blog/2012/03/windows-8-storage-spaces-bugs-and-design-flaws/
  9. ^ a b c http://www.refs-data-recovery.com/refs-recovery.aspx
  10. ^ a b c d e f g Verma, Surendra (16 January 2012). Sinofsky, Steven (ed.). "Building the next generation file system for Windows: ReFS". Building Windows 8. Microsoft. MSDN blogs. Retrieved 20 January 2013.
  11. ^ a b Meyer, David (17 January 2012). "Microsoft takes wraps off new Windows file system". ZDNet. CBS Interactive. Retrieved 20 January 2013.
  12. ^ "ReadDirectoryChangesW function". MSDN Library. Microsoft. 8 November 2012. Retrieved 21 January 2013.
  13. ^ Nagar, Rajeev (5 January 2012). Sinofsky, Steven (ed.). "Virtualizing storage for scale, resiliency, and efficiency". Building Windows 8. Microsoft. MSDN blogs. Retrieved 18 January 2013.
  14. ^ Windows Server 2012: Does ReFS replace NTFS? When should I use it? - Martin Lucas, TechNet
  15. ^ "Resilient File System Overview". TechNet Library. Microsoft. 29 February 2012. Retrieved 25 December 2013.
  16. ^ Cherry, Denny (21 August 2012). "SQL Server Pro magazine". Troubleshooting SQL Server Storage Problems. Penton Media.
  17. ^ http://www.windowsnetworking.com/articles-tutorials/windows-server-2012/refs-what-you-need-know-about-resilient-file-system-part1.html
  18. ^ http://betanews.com/2014/01/15/windows-storage-spaces-and-refs-is-it-time-to-ditch-raid-for-good/
  19. ^ http://www.phoronix.com/scan.php?page=news_item&px=MTA0NDA

Retrieved from "https://en.wikipedia.org/w/index.php?title=ReFS&oldid=675842172"