On Tue, 11 Jul 2023 at 10:45, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Not sure if SUSE has any interest in bcachefs following the massive commitment of resources to BTRFS, but it seems bcachefs needs additional resources to get over the finish line. I have no burning desire for a new FS, ext4 is just fine, but it does look interesting. I don't know if this is something the powers-that-be want to look at?
100% agree. They really, really should. In 4 years of using openSUSE on a daily basis, it destroyed its own root filesystem at least once or twice a year. Btrfs is horribly fragile if the partition fills up, and Snapper fills partitions with ease. I was only saved because I kept my `/home` filesystem on a different partition, and made very very sure it wasn't a Btrfs partition. SUSE's own docs contain a warning: « WARNING: Using '--repair' can further damage a filesystem instead of helping if it can't fix your particular issue. » https://www.suse.com/support/kb/doc/?id=000018769 So the advice I often received that I should just use one big partition for everything is absolutely the opposite thing to what I was inclined to do. Additionally, there is still no good working repair tool for Btrfs. `fsck` does not work, and the specialist tool usually makes it work. This is *not* a filesystem I would commit my enterprise data to, and the reliance on it in ALP is a very unwise move. The tagline of Bcachefs -- "The COW filesystem for Linux that *won't eat your data*" -- is extremely on-target. Make no mistake, this is a direct dig at Btrfs. And it is with good reason. I have raised this with SUSE management and got vague bland reassurances. This does the opposite of reassuring me. -- Liam Proven ~ Profile: https://about.me/liamproven Email: lproven@cix.co.uk ~ gMail/gTalk/FB: lproven@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven IoM: (+44) 7624 277612: UK: (+44) 7939-087884 Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053