ReFS was designed to overcome problems that had become significant over the years since NTFS was conceived, which are related to how data storage requirements have changed. 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 abstractionor virtualization between physical disks and logical volumes.
ReFS uses B+ trees for all on-disk structures, including all metadata and file data.[2][8] 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 35 petabytes, and a maximum volume size of 35 petabytes.[3]
ReFS employs an allocation-on-write update strategy for metadata,[2] which allocates new chunks for every update transaction and uses large IO batches. All ReFS metadata have 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 for file data; this is controlled by a new "integrity" attribute applicable to both files and directories. If file data or metadata become corrupt, the file can be deleted without taking the whole volume offline for maintenance, and then be 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[edit]
ReFS supports only a subset of NTFS features, and only supports Win32 APIs that are "widely adopted". It does not require new system APIs, and most file system filters continue to work with ReFS volumes.[2] ReFS supports many existing Windows and NTFS features such as BitLocker encryption, Access Control Lists, USN Journal, change notifications,[9]symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs, and oplock. ReFS seamlessly integrates with Storage Spaces,[2]astorage virtualization layer that allows data mirroring and striping, as well as sharing storage pools between machines.[10] ReFS resiliency features enhance the mirroring feature provided by Storage Spaces and can detect whether any mirrored copies of files become corrupt using a data scrubbing process,[8] which periodically reads all mirror copies and verifies their checksums, then replaces bad copies with good ones.
Microsoft Windows and Windows Server include ReFSUtil, a command-line utility that can be used to diagnose heavily damaged ReFS volumes, identify remaining files, and copy those files to another volume.[11]
Support for alternate data streams and hard links was initially not implemented in ReFS. In Windows 8.1 64-bit and Server 2012 R2, the file system reacquired support for alternate data streams, with lengths of up to 128K, and automatic correction of corruption when integrity streams are used on parity spaces.[13] ReFS had initially been unsuitable for Microsoft SQL Server instance allocation due to the absence of alternate data streams.[14] Hard links were introduced with preview versions of Windows Server 2022 but are not yet available in Windows 11.
ReFS was initially added to Windows Server 2012 only, with the aim of gradual migration to consumer systems in future versions; this was achieved as of Windows 8.1.[3] The initial versions removed some NTFS features, such as disk quotas, alternate data streams, and extended attributes. Some of these were re-implemented in later versions of ReFS.
In early versions (2012–2013), ReFS was similar to or slightly faster than NTFS in most tests,[15] but far slower when full integrity checking was enabled, a result attributed to the relative newness of ReFS.[16][self-published source][17][self-published source]
The ability to create ReFS volumes was removed in Windows 10's 2017 Fall Creators Update for all editions except Enterprise and Pro for Workstations.[5][why?]
Starting with Windows Server 2022 and Windows 11 21H2, the boot environment natively supports ReFS, allowing the system to be installed and run in a special way on a volume formatted with ReFS v3. If it is a volume formatted with ReFS v1, it cannot be booted with ReFS.[18]
Starting with Windows 11 build 22621.2338, ReFS is re-introduced via a Dev Drive feature; allowing fixed storage drives and VHDs to be formatted as ReFS, with special file and Microsoft Defender policies added during use.
At the Storage Developer Conference 2015, a Microsoft developer presented enhancements of ReFS expected to be released with Windows Server 2016 and included in Technical Preview 4, titled "ReFS v2".[20] It highlighted that ReFS now included capabilities for very high speed moving, reordering, and cloning of blocks between files[21] (which can be done for all blocks of a file). This is particularly needed for virtualization, and is stated to allow fast provisioning, diff merging, and tiering. Other enhancements cover the redo log (for synchronous disk writes), parallelization, efficient tracking of uninitialized sparse data and files, and efficient 4k I/O.[20]
ReFS has some different versions, with various degrees of compatibility between operating system versions. Aside from development versions of the filesystem, usually, later operating system versions can mount filesystems created with earlier OS versions (backwards compatibility). Some features may not be compatible with the feature set of the OS. The version, cluster size and other features of the filesystem can be queried with the command fsutil fsinfo refsinfo volumename.
1.2: Default version if formatted by Windows 8.1, Windows 10 RTM to v1607, Windows Server 2012 R2, and when specified ReFSv1 on Windows Server 2016. Can use alternate data streams under Windows Server 2012 R2.
2.2: Default version formatted by Windows 10 Preview build 10049 or earlier. Could not be mounted in 10061 and later.
2.0: Default version formatted by Windows Server 2016 TP2 and TP3. Could not be mounted in Windows 10 Build 10130 and later, or Windows Server 2016 TP4 and later.
3.0: Default version formatted by Windows Server 2016 TP4 and TP5.
3.1: Default version formatted by Windows Server 2016 RTM.
3.2: Default version formatted by Windows 10 v1703 and Windows Server Insider Preview build 16237. Can be formatted with Windows 10 Insider Preview 15002 or later (though only became the default somewhere between 15002 and 15019). Supports deduplication in the server version.
3.3: Default version formatted by Windows 10 Enterprise v1709 (ReFS volume creation ability removed from all editions except Enterprise and Pro for Workstations starting with build 16226; read/write ability remains[5]) and Windows Server version 1709 (starting with Windows 10 Enterprise Insider Preview build 16257 and Windows Server Insider Preview build 16257).
3.4: Default version formatted by Windows 10 Pro for Workstations/Enterprise v1803 and newer, also server versions (including the long-time support version Windows Server 2019).
3.5: Default version formatted by Windows 11 Enterprise Insider Preview (build 19536 or newer); adds support for hard links (only on fresh formatted volume; not supported on volumes upgraded from previous versions).[3]
3.6: Default version formatted by Windows 11 Enterprise Insider Preview (build 21292 or newer) and Windows Server Insider Preview (build 20282 or newer)
3.7: Default version formatted by Windows 11 Enterprise Insider Preview (build 21313 or newer) and Windows Server Insider Preview (build 20303 or newer). Also, the version shipped with the final releases of Windows Server 2022 and Windows 11. Added file-level snapshot (only available in Server 2022).
3.9: Default version formatted by Windows 11 Enterprise Insider Preview (build 22598 or newer) and Windows Server Insider Preview (build 25099 or newer). Added post process compression with LZ4 and ZSTD and transparent decompression.
3.10: Default version formatted by Windows 11 Enterprise Insider Preview and Windows Server Insider Preview (build 25324 or newer).
3.12: Default version formatted by Windows 11 Enterprise Insider Preview (build 26002 or newer).
This article needs to be updated. Please help update this article to reflect recent events or newly available information.(February 2019)
Issues identified or suggested for ReFS, when running on Storage Spaces, include:
REFSutil does not work on 3.7 (Windows 2022)
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.[23] This can happen, for example, if the physical disks underlying a storage space became 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.[23]
Thin-provisioned ReFS on top of Storage Spaces, occasionally if the ReFS partition is extended to the full size of the thin-volume. When later extending the thin-volume size the ReFS partition may fail to extend to the thin-volume size. Once it fails to extend the partition you can never again extend the partition, no matter how large you extend the thin-volume size too. The workaround is to never extend the ReFS partition to the full size of the thin-volume, always leave a few GB at the end of the volume unassigned. The problem still exists in Server 2022. It is thought that during the extension of the partition, it writes values into the partition table that corrupt the table when using the full size of the thin-volume, preventing any further expansions. That data is still intact and the ReFS partition works normally. A solution is to create a new volume and ReFS partition and copy out of the old ReFS and into the new ReFS requiring double storage during the copy before the old volume can be deleted.
Thin-provisioned volume formatted with ReFS eventually expands the thin volume to the full size of the ReFS formatted size, nullifying the reason to use a thin volume on Windows 10. The more use the partition sees the quicker the volume is expanded, even if the data is mostly static. Less used drives still expand on Windows 10 but not at the same rate. When using an NTFS formatted volume on top of a thin volume does not experience the same expansion. For example, 4 TB ReFS two-way mirror 99% static data(data logs) 1.11 TB used, data does not change once added, data added once a month, storage spaces used the entire 8 TB of storage(should be around 2.2 TB used in storage spaces). Same storage space different thin volume formatted with ReFS, two-way mirror single data write, but data is used less frequently and added to less frequently 257 GB of data, storage spaces using 7.77 TB. thin volume NTFS partition, used in the same manner as the 257 GB partition, but only using 601 GB. 7-month window.
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.[citation needed]
Like ReFS, ZFS, Bcachefs, and Btrfs are designed to integrate data protection, snapshots, and background error correction.
In 2012, Phoronix wrote an analysis[25] of ReFS vs Btrfs. At the time, their features were similar, with both supporting checksums, RAID-like use of multiple disks, and error correction. However, ReFS lacked copy-on-write snapshots and compression, both found in Btrfs and ZFS.
In 2014, BetaNews wrote a review of ReFS and assessed its readiness for production use.[26] The review concluded that ReFS had at least some advantages over two of its main file system competitors.
ZFS (used in Solaris, illumos, FreeBSD and others) was widely criticized for its comparatively extreme memory requirements of many gigabytes of RAM for online deduplication. However, online deduplication was not enabled by default in ZFS and was not supported at the time by ReFS (it has since been added), so not enabling ZFS online deduplication yielded a more even comparison between the two file systems as ZFS then has a memory requirement of only a few hundred megabytes.[27]
Offerings such as Drobo used proprietary methods which have no fallback if the company behind them fails.
As of November 2019[update], Microsoft has not published any specifications for ReFS, nor have any working open-source drivers been made. A third-party open-source project to document ReFS is on GitHub.[28][29]
^ abc"Windows 10 features and functionality removed in Windows 10". docs.microsoft.com. 30 January 2020. Archived from the original on 18 November 2019. Retrieved 23 February 2020. Creation ability will be available in the following editions only: Windows 10 Enterprise and Windows 10 Pro for Workstations. Creation ability will be removed from all other editions. All other editions will have Read and Write ability.
