Resilient file system (ReFS) is developed by Microsoft and released with Windows server 2012 to lead the tech world in all tenses. As the name itself explains the whole. To be briefed, the Resilient File System is one of the local file system developed in the intent of maximizing data availability and protecting the data at the time of crucial system errors.

The REFS is designed in a way to suite the evolving storage industry in a secured manner. So it makes use of B+ trees to be updated in dealing with the Meta data and actual data pointers. And in security related issues, REFS maintains pro-activeness in reacting to the error messages on storage spaces.

Interior Design:

On looking at the interior of the REFS it can be classified in two parts

  • Upper layer
  • On-disk store engine

The upper layer of Resilient FileSystem makes use of New Technology File System (NTFS). In depth it has borrowed the API compatibility, Bit locker encryptions, mount point, reparse points, file Ids and oplocks etc.

The on-disk store engine part handles the data structure and their manipulation. This is where the B+ trees are implemented. A single B+ tree common is in control of the REFS on-disk structure. Since it can be updated, the REFS is more flexible. It also has a new notion of tables which use generic key value combinations to the indexed tables. Roughly we could say that the file accessing and retrieval time will be handled more effectively.

The ReFs is supported by Windows Server 2012 or Windows Server 8 and Windows 8x versions.


To be explained short the REFS advances in resiliency, robustness, Integrity and compatibility with the existing API, and apart from this, the other merits are…

  • The robust update of disk helps to access the drive volumes in agile manner, absence of which is a major draw back in other file systems
  • Instead of storing the meta information in log format the REFS make use of a new atomic fashioned format which relies on “shadow paging technology”
  • Since the REFS uses single B+ tree structure the file system will never go offline. That means information lost on “application not responding” problem is reduced
  • Stores the system Meta data in protected way by using generic key value
  • Designed in a way to accept updates in the future
  • No need to convert NTFS file to REFS as it supports NTFS data readily


  • Though the Resilient File System makes use of NTFS feature it lacks in some areas where NTFS advances. The missing out things are hard links, extended attributes, object Ids and data deduplication
  • The Automatic error correction is highlighted as main advantage. But it is supported only in mirrored spaces (process of saving the files in two or more drives to ensure safety)
  • If the cache manager is broken then it leads to a BSOD
  • Cannot be used in devices like pen drives, memory cards, flash drives and other removable devices
  • It cannot be used in drives for bootable purpose
Safe and Secure
Safe and Secure