编辑“︁ReFS”︁（章节）

=== 已移除功能 ===
某些NTFS功能在ReFS的初始版本中已移除或不支持。这包括[[备用数据流]]、[[NTFS重解析点|对象ID]]、[[8.3|8.3文件名]]、[[NTFS|NTFS压缩]]、[[加密文件系统]]（EFS）、{{tsl|en|Transactional_NTFS|事务性NTFS}}、[[硬链接]]、[[扩展文件属性|扩展属性]]和{{tsl|en|Disk_quota|磁盘配额}}。<ref name="B8_ReFS"/><ref name="zdnetrefsunveiled"/><ref name="Lucas">{{Cite web |url=http://blogs.technet.com/b/askpfeplat/archive/2013/01/02/windows-server-2012-does-refs-replace-ntfs-when-should-i-use-it.aspx |title=Windows Server 2012: Does ReFS replace NTFS? |access-date=2016-06-26 |archive-url=https://www.webcitation.org/6GdtBVrBz?url=http://blogs.technet.com/b/askpfeplat/archive/2013/01/02/windows-server-2012-does-refs-replace-ntfs-when-should-i-use-it.aspx |archive-date=2013-05-15 |dead-url=yes }}</ref>ReFS最初不提供[[重复数据删除]]，<ref name="B8_ReFS"/>在随后的v3.2版本中实现。此外，Windows目前不能从ReFS卷引导启动。<ref name="B8_ReFS"/>镜像或条带化卷的动态磁盘已被“存储空间”提供的镜像或条带化存储池取代；自动纠错仅在镜像空间支持。<span class="cx-segment" data-segmentid="185"></span>

在后续实现的Windows 8.1 64位和Server 2012 R2的ReFS中，文件系统开始支持备用数据流，最大长度128K，以及完整性流在奇偶效验空间上自动纠正损坏数据。<ref>{{Cite web|url=http://technet.microsoft.com/en-us/library/hh831724.aspx|title=Resilient File System Overview|accessdate=2013-12-25|date=2012-02-29|publisher=[[Microsoft]]|website=[[Microsoft TechNet#Library|TechNet Library]]|archive-date=2017-02-01|archive-url=https://web.archive.org/web/20170201111121/https://technet.microsoft.com/en-us/library/hh831724.aspx|dead-url=no}}</ref>ReFS在缺乏备用数据流的支持时不适合[[Microsoft SQL Server]]实例分配。<ref>{{Cite web|url=http://sqlmag.com/blog/sql-server-and-windows-server-2012s-refs-file-system|title=SQL Server Pro magazine|date=2012-08-21|last=Cherry|first=Denny|publisher=[[Penton Media]]|website=Troubleshooting SQL Server Storage Problems|access-date=2016-06-26|archive-url=https://web.archive.org/web/20171010052123/http://sqlmag.com/blog/sql-server-and-windows-server-2012s-refs-file-system|archive-date=2017-10-10|dead-url=yes}}</ref>
<!-- 截至2015年3月，WIndowsNetworking.com对ReFS状态的评论指出：<ref>{{Cite web|url=http://www.windowsnetworking.com/articles-tutorials/windows-server-2012/refs-what-you-need-know-about-resilient-file-system-part1.html|title=ReFS: What you need to know about the Resilient File System (Part 1)|work=WindowsNetworking.com}}</ref>
: "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." -->