• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ReFS failure

Doomer

Diamond Member
Well hell, why did I trust a brand new Windows file system from Microsoft? How could I be so stupid??

Described here - http://www.refs-data-recovery.com/

The drive in question passed diags with flying colors and after returning to NTFS, it's been flawless.

DON'T TRUST YOUR VALUABLE DATA TO THIS NEW FS !!!!

Fortunately I had a backup so all I lost was me time. I have a couple of other drives formated ReFS and I'm in the process of returning them to NTFS.
 
lolol... ReFS was supposed to be the next greatest thing tho...

Something is seriously wrong with microsoft these days...

Anyhow i got sick on the dashboard of server 2012, the dashboard on server didnt make any sense...
How are you holding up to it tho?
 
No way to tell. The data was inaccessible. Click on the drive and it attempts a repair and returns the message as per the link above.

As for dealing with Server 2012, I installed a 3rd party start button and pretend the metro garbage doesn't exist.
 
"Although ReFS is introduced as a filesystem which resists to various failures, nevertheless, practice shows that ReFS does fail."

Duh. It is why we keep backups.

2012 Is fantastic however and beats 2008R2 hands down. Hoping they drop the start menu on it for 2012.1 so using terminal services with it isn't so frustrating.

--edit--

Also as a side note, ReFS was designed to be used with storage spaces for redundancy. It is a bit like ZFS in that the most useful parts of ZFS don't operate with only a single disk. Otherwise the ReFS.sys driver itself is running "chkdsk" on the disk when ever the disk is in operation. It is supposed to use the redundant copies on other disks to rebuild or put forward a best effort to recover. Something glitched on that disk and damaged the Btree structure in a way that it couldn't recover.
 
Last edited:
I migrated all my drives back to NTFS. Think I'll wait till all the bugs are discovered and weeded out of ReFS before trying it again. Just wanted to give you guys a heads up that you could loose data using it.
 
Back
Top