REFS File System

>>61178191
Microsoft deprecated it a few years ago. Windows 10 doesn't even support it out of the box.

>>61178199
>Microsoft deprecated it a few years ago. Windows 10 doesn't even support it out of the box.

https://forums.mydigitallife.net/threads/refs-support-in-windows-10-creators-update-v1703.73874/

>ReeeeeeeeeeeeeeeeeeeeFS

>>61178191
>REFS
I tried using it to make an array with a couple different sized disks. It's a piece of shit that craps itself if everything isn't the exact same size.
>use 100 GB in a 4 TB array
>get errors about it being full
The smallest drive in it was fucking 250 GB so I have no idea how the fucked up enough to make it shit itself after a hundred.

>>61178725
you need to change your provisioning from thin to fixed. you need to delete the entire thing and start from scratch

>>61178191
been running if for awhile, it's pretty much trash tier.
no shadow copy, dedup, quotas, compression or encryption.
jbod raid performance is shit, the tiered storage doesn't seem to do what it's supposed to do and if you want to remove/add or make changes the feature you need to delete the while raid.


Stick to zfs btrfs

>>61179041
>you need to delete the entire thing and start from scratch
I did and I went with ZFS instead.

>>61178191
Does it have double/triple parity?

>>61179072
good choice, anon

Available options with REFS are:
Simple Volume = Zero protection
Two Way mirror = Raid 1
Three Way Mirror = Data is copied to three drives, can lose any two drives before data is gone, needs 5 drives at minimum
Also can enable (via powershell) data checksum for whole volumes so if a file is corrupt it can be replaced with a good copy. Must use it in conjunction with Two/Three way mirror option though before this is useful. There is third option and that is create a Parity volume (Raid-5) but you can't use REFS with it only NTFS for some reason. Now this is what is available with Server 2012R2, in Win Ten/Server 2016 they might have changed things a bit.

I think the whole bitrot thing has gotten way way outta hand. Your most common causes of bitrot (data corruption) are hardware failure (Drives/add in cards) or due to sudden power failures/improper shutdowns the data doesn't get written/parity checks done completely. Backups and a UPS will solve these two problems to a point. Nothing is perfect. But using both will mitigate the problem. Alternative oses, no mater what kind of file system they use are still bound by these two things (hardware & power) and are still subject to these issues.

Screw Server 2012/REFS/FreeNas/etc. My current WHS 2011 server has been running fine. I have backups,I have raid, and I use a UPS to shutdown the server properly if the main power fails. It ain't like I'm supporting 5000 users who'll kill me if the server is down for maintenance issues (drive failure/expansion)