-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sat, 2020-06-27 at 12:37 -0700, Gerald B. Cox wrote: > I was an early adopter and used BTRFS for many years, singing its > praises. > I was particularly interested in the RAID capabilities. Then in 2016 > the > bomb was dropped that: > > "It turns out the RAID5 and RAID6 code for the Btrfs file-system's > built-in > RAID support is faulty and users should not be making use of it if > you care > about your data. Well, the RAID5 and RAID6 in Btrfs is still not really working fine and there are some threads in linux-btrfs@ at kernel ML. Workstation users are not using RAID (even if they do, I am not even sure how it is configured today with Anaconda). Even for those that do, RAID0/1/10 seems to be working just fine with Btrfs. RAID5/6 is definitely not something that people run on their laptops. > There has been this mailing list thread > < > https://www.mail-archive.com/linux-btrfs@xxxxxxxxxxxxxxx/msg55161.html > > > since the end of July about Btrfs scrub recalculating the wrong > parity in > RAID5. The wrong parity and unrecoverable errors has been confirmed > by > multiple parties. The Btrfs RAID 5/6 code has been called as much as > fatally > flawed > < > https://www.mail-archive.com/linux-btrfs@xxxxxxxxxxxxxxx/msg55179.html > > -- > "more or less fatally flawed, and a full scrap and rewrite to an > entirely > different raid56 mode on-disk format may be necessary to fix it. And > what's > even clearer is that people /really/ shouldn't be using raid56 mode > for > anything but testing with throw-away data, at this point. Anything > else is > simply irresponsible." > > The current situation as I understand it is the problem is "mostly > fixed" - > whatever that means. > > So, BTRFS is great, ready for prime time... many people are using it, > etc. > etc. etc. until something goes wrong and then you get... well, it's > experimental and not intended for production. Sucks to be you. > > At some point you have to fish or cut bait. I was under the > impression > that Redhat had done exactly that with the announcement and direction > of > Stratis. > > Why are we not concentrating on Stratis and XFS? Seems to me after > waiting > for almost a decade for the promise of BTRFS to be fulfilled and then > having so many > people be burned, we should be turning the page rather than > continuing to > rehash the same old arguments. Well, because those have different use-cases? One of the problems with XFS is that you can't shrink it. With systemd-homed on the horizon, it will become a problem. It also does not like much when power goes down (even with battery on laptops it is not uncommon), two my colleagues got XFS destroyed (for one of them, twice) when they had to turn off their laptops using power button in last ~2years. Then they have switched to ext4 and nothing like that has happened again. But that one does not have features that are very useful on laptops. Stratis uses XFS under the hood, so it has same problem, but also it still can't be used as a root filesystem. And generally it is designed for different use-case than a workstation. > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx - -- Igor Raits <ignatenkobrain@xxxxxxxxxxxxxxxxx> -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcwgJ58gsbV5f5dMcEV1auJxcHh4FAl73qagACgkQEV1auJxc Hh7sthAAg+omUP71jyuAEXoy1/+B3m+OSikBEAxRS055en4JaKROLQ2UVJOSCzs+ KSJkg413ex8ORxH3l8vhnIlWCVXwV8de2duAt85DpknGe0XHpnLTtC45/xejUiln tjpz8RqyEYTXMEE7KhJpc3KCLgN1VHyVtr+6Y0P1WUOBQWj1iF5kfrB5J+VhYpVO qygMcjlSiFtJW4gfs8siukSebn1t3ILGX9eOvxjhNGgrsfZ4bboq5N4rhFb2+NWF sjBmjE9qIFJK21xgp1XPJHiF4SsfL8CQZqgvBGYcnfmcGb7wiXPZEvzVJ5VVSNh2 7l4VWrix+YDXKmhD7WccCLZOjEGJg7CSOHndm6FPQt6++OGMsWUdmZNAsB9Iw6Ia Y5oDYuVxRqH5VLPKwKfb4FIQJDr/RESJU7Xd9W0+RPwjLb73k6sPyn3eWBMbiWaa 5e8G/GlWJtT1GGQT3fBnUtKhRBrCJQ/tH/oDmWQ7BLgUWisiU2eOaMB3MCWDq13F uaKB63CU8EnvdDJGCbjy0U+D/e2ZRD8tKNcJAn1dl8+sBD28/vd5cO2aTv4AYSjG Jf9e7RHTy+giMx4jvKbPaQb6187Im92C/7J8rBuk7PhLhtZQU7RM5CPj9aiqYkWg 7OoNVWQSRbljS0V3J0qsUmvwXf5PngLjCKqBot2vbZIV7FM0sls= =Q/6i -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
