Linked by malxau on Tue 17th Jan 2012 13:34 UTC
Windows Along with Storage Spaces coming in Windows 8, ReFS forms the foundation of storage on Windows for the next decade or more. Key features of the two when used together include: metadata integrity with checksums; integrity streams providing optional user data integrity; allocate on write transactional model for robust disk updates; large volume, file and directory sizes; storage pooling and virtualization making file system creation and management easy; data striping for performance and redundancy for fault tolerance; disk scrubbing for protection against latent disk errors; resiliency to corruptions with "salvage" for maximum volume availability in all cases; and shared storage pools across machines for additional failure tolerance and load balancing.
Thread beginning with comment 503772
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: What Will Be Removed
by hechacker1 on Tue 17th Jan 2012 17:05 UTC in reply to "RE[3]: What Will Be Removed"
Member since:

It's implemented as a scrub job that runs in the background to deduplicate data after the fact.

Edited 2012-01-17 17:19 UTC

Reply Parent Score: 1

RE[5]: What Will Be Removed
by kragil on Tue 17th Jan 2012 17:16 in reply to "RE[4]: What Will Be Removed"
kragil Member since:


Q) How come ReFS does not have deduplication, second level caching between DRAM & storage, and writable snapshots?

ReFS does not itself offer deduplication. One side effect of its familiar, pluggable, file system architecture is that other deduplication products will be able to plug into ReFS the same way they do with NTFS.

Reply Parent Score: 2

RE[6]: What Will Be Removed
by hechacker1 on Tue 17th Jan 2012 17:20 in reply to "RE[5]: What Will Be Removed"
hechacker1 Member since:

Hmm, a tradeoff I suppose.

NTFS supports deduplicatation in server 8.

I take back what I said about ReFS then. It doesn't supercede all the needed features.


Thinking about it for a minute, it does seem kind of a weird omission considering the support is already there for NTFS for dedup.

But I guess the reason they decided to not support it is because it goes against having redundancy in the system. They specifically mention you only get checksum repairing when using mirrored storage pools, not parity. Though with parity errors are still logged with checksums.

Still, it leaves an interesting opening for dedup while using ReFS. I know there is software that allows you to layer one file system on top of another. Presumably, you could layer an NTFS volume on top of ReFS to get advantages of both, but probably suffer a performance hit.

Or just wait for Microsoft to implement it in future versions.

Edited 2012-01-17 17:40 UTC

Reply Parent Score: 1