On 6/26/20 12:31 PM, Chris Murphy wrote:
That pattern will change with btrfs. There will be fewer of some
more of others, and the messages will be different. fsck.ext4 is
pretty much all we have, all we're used to, and it's a binary
pass/fail. Even though we're talking about edge cases at this level,
those who get unlucky for whatever reason are going to need a
community of user to user support giving them good advice. Will Fedora?
Well said. BTRFS is more complex and will require getting used to.
In case of FS trouble, everyone knows 'fsck' but as Josef wrote
With btrfs you are just getting started. You have several built in
mount options for recovering different failures, all read only. But you
have to know that they are there and how to use them.
which is both encouraging and terrifying :)
I remember that two issues that made me apprehensive wrt. BTRFS were its
handling of the 'disk full' situation, and lack of a staightforward
'fsck' workflow. I think the first issue has been resolved, and we
probably just need some docs and scripts that handle file system
corruption by remounting R/O and printing some suggestions what to do next.
It's also important to talk about what's left on the table*without*
this change. The potential to almost transparently drop in a new file
system that extends the life of user's hardware, eliminates the free
space competition problem between /home and /, and allocates it more
efficiently. And asks*less* of day to day users, while inviting
*more* from those who want to explore more features. On the same file
For what it's worth, this is really needed, and overdue. I have
repeatedly failed Fedora OS release upgrades on different machines by
running out of root fs space. I think the default / is around 50GB, and
it's too easy to fill: during OS update we need space for three copies
of each package: the old version, the downloaded new version, and the
space to install the new version.
Even though technically dnf system-upgrade can --download-dir to a
location off / it doesn't seem to work with the actual upgrade, so the
only way I know is to delete largest packages (flightGear*, piglit*,
KiCAD*, ...) and reinstall them after update.