On Tue, 2015-11-24 at 02:51 +0000, Dimitri John Ledkov wrote: > This is currently the case for xfs and btrfs, which imho is silly. Well sooner or later, btrfs check is declared stable and then I think we do want to have regular checks (though don't know whether this is upstream's recommendation).
In fact, btrfs seems to be quite useful already these days... > I'm proposing to do following, for filesystems that require no > periodic maintainance: > - initramfs-tools to not include fsck.$foo tools for passno=0 > mountpoints IMHO, initramfs hooks should generally the tree of stacked block devices/containters/fs (e.g. MD, dmcrypt, lvm, etc.) for the necessary devices (typically root and resume?) and only include those tools actually required. > - on upgrade force set passno to zero for filesystems in question uhm... you mean changing around in user's /etc/fstab? Sounds not appealing. > Feedback? Questions? Concerns? I'm a bit sceptic that there is really something like a fs that requires no periodic maintenance... I've already had some issues found with btrfs check, even though one of them proved to be a bug in btrfs check itself (which is right now being hunted down by one of the developers). It's already some years ago I've used XFS, but then I regularly ran xfs_repair in scan-mode... and I think I remember that issues were found, which weren't during running system. But a lot has happened to XFS since then. I'd rather say, ask usptream whether they'd suggest to run btrfs check on boot (in non-destructive mode) Cheers, Chris. >
smime.p7s
Description: S/MIME cryptographic signature
