matt40k (24th January 2012)
The Register has just put up an article about the new file system that Server 8 and ultimately W8 will utilise, the Resilient File System (ReFS): Microsoft raises 'state of the art' son of NTFS ? The Register
You can also read more about this on the W8 blog here: Building the next generation file system for Windows: ReFS - Building Windows 8 - Site Home - MSDN Blogs
matt40k (24th January 2012)
"Never take the file system offline. Assume that in the event of corruptions, it is advantageous to isolate the fault while allowing access to the rest of the volume. This is done while salvaging the maximum amount of data possible, all done live."
Now that sounds good! if they can live up to what they claim, i think this is going to be awesome!
(the whole no GUI thing going on with Server 8 has got me excited too. I personally think its going to be a good move forward for sysadmins..)
Helge Klein's blog has a great overview of the features ReFS does and doesn't support.
- Allocate on write for metadata: new metadata is written to a different location. If the write fails, the existing metadata is still intact.
- Checksums protect all metadata.
- Integrity streams are optional checksums for file content. May be disabled for databases, for example.
- Scrubbing: On ReFS volumes residing on a mirrored Storage Space a system task periodically scrubs all metadata and Integrity Streams. Scrubbing involves reading all the redundant copies and validating their correctness using the ReFS checksums. If checksums mismatch, bad copies are fixed using good ones.
- Salvage is a feature that keeps the volume online and intact even if corrupt data is detected. In that case, only the corrupt data is removed from the namespace while the rest of the volume remains unaffected.
What Still Works
ReFS works with the following well-known file system technologies:
- Access control lists
- USN journal
- Change notifications
- Symbolic links
- Mount points
- Reparse points
- Volume snapshots
- File IDs
What Does Not
ReFS does not support the following well-known file system technologies:
- Named streams (this probably means Alternate Data Streams)
- Object IDs
- Short names (8.3 names)
- EFS encryption
- User data transactions (this probably means the Transactional NTFS, TxF, introduced with Vista)
- Sparse files
- Hard links
- Extended Attributes
Removing quotas seems odd as well, although I suspect Storage Spaces might include that functionality.
The short 8.3 filenames are stored separately from the standard (long) filenames so disabling them shouldn't cause problems.Code:fsutil behavior set disable8dot3 c: 1
pmsl so will this sort out profile issues then haha
There are currently 1 users browsing this thread. (0 members and 1 guests)