Default passno for XFS in fstab is 0: https://salsa.debian.org/installer-team/partman-xfs/blob/63/fstab.d/xfs#L24 Because of this, fsck hook does not add fsck.xfs. Fine up to xfsprogs 4.15.1, since fsck.xfs does nothing. However, starting with xfsprogs 4.16.0, fsck.xfs runs xfs_repair when called with -f (forcefsck|fsck.mode=force): https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=7c3e94a3001292946521fb4cfac841e9ac32691b https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=04a2d5dcdc0486e2b0c9903428a17313b8c92b7d So having fsck.xfs and xfs_repair in the initramfs is useful now. passno must stay 0 because verification is only done in force mode. (xfsprogs is outdated in sid right now)
Control: reassign -1 xfsprogs I think xfsprogs should take responsibility for adding the necessary files to the initramfs. It doesn't make sense for initramfs-tools to have to know about quirks like this. (There is precedent for this; btrfs-progs installs its own initramfs-tools hook.) Ben.
I am lost trying to change this bug severity to normal again. Help appreciated! :-)