SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
Recommended by:
goldworldnet
From: FJB7/13/2019 1:29:22 PM
1 Recommendation  Read Replies (1) of 110613
 
ReFS

From Wikipedia, the free encyclopedia

Microsoft
Resilient File System
1 August 2012; 6 years ago [1]with Windows Server 2012
B+ tree [2]
1 yobibyte (280 bytes)
16 exbibytes[ citation needed](264-1 bytes)
Yes
No
Yes, since v3.2 debuting in 2016 v1709 [3]
Yes

Windows Server 2012 and later Windows 8.1 and later (ReFS volume creation ability removed in Windows 10's 2017 Fall Creators Update, except for Windows 10 Enterprise and Pro for Workstations [4])
docs.microsoft.com/en-US/windows-server/storage/refs/refs-overview








Resilient File System (ReFS), [5] codenamed "Protogon", [6] 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 problems that had become significant over the years since NTFS was conceived, which are related to how data storage requirements had changed. The key design advantages of ReFS include automatic integrity checking and data scrubbing, removal of the need for running chkdsk, protection against data degradation, built-in handling of hard disk drive failure and redundancy, integration of RAIDfunctionality, a switch to copy/allocate on write for data and metadata updates, handling of very long paths and filenames, and storage virtualization and pooling, including almost arbitrarily sized logical volumes (unrelated to the physical sizes of the used drives).

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; this was achieved as of Windows 8.1. [7] 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, [8] but far slower when full integrity checking was enabled, a result attributed to the relative newness of ReFS. [9] [10] Pre-release concerns were also voiced by one blogger[ who?] over Storage Spaces, the storage system designed to underpin ReFS, which reportedly could fail in a manner that prevented ReFS from recovering automatically. [11] [12] [13]

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, [4] which would seem to indicate Microsoft is no longer intending ReFS as a general replacement for NTFS, at least in the near future.

The cluster size of a ReFS volume is either 4 KiB or 64 KiB. [14]
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext