News for hackers. Stuff that matters.
Re:Raid-Z Expansion Feature for ZFS Goes Live by namibj on Tuesday February 08, 2022 @06:29PM (#30266383)
Btrfs lets you keep metadata at a stronger bitrot-protection level fairly easily, and as long as that is still ok, you'll only use the data blocks that rotted, so at LTT's scale just a few seconds of footage in total.
Re:Raid-Z Expansion Feature for ZFS Goes Live by NavinF on Tuesday February 08, 2022 @06:34PM (#30266423)
Even if that’s true, btrfs would be entirely impractical for them because btrfs-raid6 is broken. Their petabyte server would become a 1/3 petabyte server without raidz2.
Re:Raid-Z Expansion Feature for ZFS Goes Live by namibj on Tuesday February 08, 2022 @06:50PM (#30266559)
But that's more because no one dared to try and actually fix Btrfs parity raid. Misaligned incentives causing lack of funding for something as flexible and generally resilient as Btrfs.
Re:Raid-Z Expansion Feature for ZFS Goes Live by guipsp on Tuesday February 08, 2022 @07:09PM (#30266701)
My data doesn't really care if the reason for brtfs losing data is lack of funding
Re:Raid-Z Expansion Feature for ZFS Goes Live by matheusmoreira on Tuesday February 08, 2022 @10:58PM (#30268614)
Can you elaborate on this? I see NAS companies like Synology using btrfs in their products. I don't understand why btrfs RAID 5/6 is still not stable.
Re:Raid-Z Expansion Feature for ZFS Goes Live by genghizkhan on Tuesday February 08, 2022 @11:57PM (#30269011)
Synology deploys btrfs on top of md-raid. They do not trust btrfs's raid layer.
Re:Raid-Z Expansion Feature for ZFS Goes Live by namibj on Wednesday February 09, 2022 @12:35AM (#30269267)
Because there are some write holes around iirc power failures and, more importantly, restore basically doesn't work (the code just doesn't exist in a working variant).

This isn't easy code to write, and it's Linux-Kernel-C, far from "comfy" code to write. I assume it's that kind of effect that continues to keep all competent people from fixing Btrfs's RAID 5/6 code. (If I could gather the motivation, I could probably do it, but that's far from fun to do and I'm already dire for motivation-to-code... it needs to be someone who likes that work, ideally sponsored so they don't loose money from working on that project.)

Re:Raid-Z Expansion Feature for ZFS Goes Live by mustache_kimono on Tuesday February 08, 2022 @06:48PM (#30266535)
> Btrfs lets you keep metadata at a stronger bitrot-protection level

I really have no idea what BTRFS feature this refers to, but ZFS stores redundant copies of metadata. See: redundant_metadata, https://zfsonlinux.org/manpages/0.8.0/man8/zfs.8.html

Re:Raid-Z Expansion Feature for ZFS Goes Live by namibj on Tuesday February 08, 2022 @06:52PM (#30266577)
Block group specific profiles. The normal these days is SINGLE for data and DUP for metadata.

See how one converts here: https://btrfs.readthedocs.io/en/latest/btrfs-balance.html

Re:Raid-Z Expansion Feature for ZFS Goes Live by mustache_kimono on Tuesday February 08, 2022 @07:03PM (#30266652)
Okay, I still don't understand your point.

BTRFS stores duplicate copies of the metadata. Good for BTRFS. I don't understand how this would have prevented what LTT experienced.

First, as someone else said -- no one would use a BTRFS raid5/6 array in production. No one. Second, I don't think what LTT experienced was bit rot. There were far, far too many data errors for that be simple bit rot. My guess is bad cable, bad HBA which maybe doesn't support something like ASPM, etc. Third, are we even sure the problem was corrupted metadata? Fourth, ZFS keeps redundant copies of metadata too (as do many filesystems.)

So the question is what's your point?

Re:Raid-Z Expansion Feature for ZFS Goes Live by InvaderFizz on Tuesday February 08, 2022 @11:37PM (#30268885)
Plenty of people do, like my predecessors at a former job. I then had to clean up the blast from multiple BTRFS RAID6 arrays.

Oh, you meant no one with a shred of responsibility, which I agree with.

Re:Raid-Z Expansion Feature for ZFS Goes Live by namibj on Tuesday February 08, 2022 @07:09PM (#30266703)
That you could have dialed up the redundancy for metadata to 3x or even 4x copies being stored, and just because a block got bitrot doesn't mean other blocks fail to read.

I know no one would use Btrfs raid5/6 in production, but that's because no one wanted to enough to get the required development done.

If it was just file blocks that got corrupted, there would be just very minor damage in total and a scrub that logs all damaged blocks typically proceeds at sequential read speeds from what I've observed in the past.

Re:Raid-Z Expansion Feature for ZFS Goes Live by chungy on Tuesday February 08, 2022 @07:29PM (#30266916)
ZFS already stores three logical copies of all metadata, regardless of copies parameter or vdev redundancy. The failures LTT experienced went way beyond what ZFS, or btrfs, could repair.

They made severe errors in judgment when setting up the system and failing to monitor and administer it. No system will ever protect against this. Not ZFS. Not btrfs.