Btrfs In Linux 3.10 Gets Skinny Extents, Quota Rebuilds

[brosis]

I broke btrfs on accident one time during an install of F18 because I accidentally killed the power to it (Pulled the wrong cable >.>) during an update. I didn't try to fix it though, for all I know a quick 'btrfsck /dev/sda1' would've fixed it, instead since it was a brand new install I just redid it.

And I know btrfs can detect even a single bit of corruption, that got mentioned in a review of it that Michael covered-- the company's raid hardware was failing and btrfs noticed one bit was corrupted so far, printed warnings and then the failing hardware was caught.

Thanks for response! But I meant a more serious, analytic breaking of stuff to prove wither its more (or less) reliable than existing solutions like EXT.

Bitrot ofc gives BTRFS bonus points, no questions.

[Ericg]

Thanks for response! But I meant a more serious, analytic breaking of stuff to prove wither its more (or less) reliable than existing solutions like EXT.

Bitrot ofc gives BTRFS bonus points, no questions.

As far as purposefully breaking it... i haven't seen anyone tried with recent kernels. Keep in mind, up until like 2 or so releases ago, btrfs had some outstanding corruption bugs so everyone complained, they got fixed, but I dont think anyone has done real tests since then. You'll probably hear about a few coming soon since SUSE has marked it as Production Ready, and im sure RHEL 7 will include it as an option.

[juxtatux]

I broke btrfs on accident one time during an install of F18 because I accidentally killed the power to it (Pulled the wrong cable >.>) during an update. I didn't try to fix it though, for all I know a quick 'btrfsck /dev/sda1' would've fixed it, instead since it was a brand new install I just redid it.

And I know btrfs can detect even a single bit of corruption, that got mentioned in a review of it that Michael covered-- the company's raid hardware was failing and btrfs noticed one bit was corrupted so far, printed warnings and then the failing hardware was caught.

Just like that other indestructible b-tree hive, windows registry, BIT for BIT... completely reproducible on dd copies!