FS#53543 - fsck failed with error code 8

Attached to Project: Arch Linux
Opened by Shixin Zeng (szeng) - Monday, 03 April 2017, 00:50 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 15 June 2017, 07:17 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

This is what I saw from "journalctl -b"
Apr 02 16:37:37 localhost systemd-fsck[160]: fsck: /usr/local/sbin/fsck.xfs: execute failed: No such file or directory
Apr 02 16:37:37 localhost systemd-fsck[160]: fsck failed with error code 8.
Apr 02 16:37:37 localhost systemd-fsck[160]: Ignoring error.

It seems that systemd-fsck is looking for fsck in a wrong directory. The fsck.xfs on my system is under /sbin, and /usr/bin/:
$ ls /sbin/fsck.xfs
/sbin/fsck.xfs
$ ls /usr/bin/fsck.xfs
/usr/bin/fsck.xfs
$ /usr/local/sbin/
-bash: /usr/local/sbin/: Is a directory

It's the same path in initramfs:
$ lsinitcpio /boot/initramfs-linux-lts.img |grep fsck
usr/bin/fsck
usr/bin/fsck.xfs
usr/lib/systemd/systemd-fsck
usr/lib/systemd/system/systemd-fsck@.service
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 15 June 2017, 07:17 GMT
Reason for closing:  Not a bug
Additional comments about closing:  There is no fsck for xfs or btrfs
Comment by Dave Reisner (falconindy) - Monday, 03 April 2017, 14:53 GMT
Well, xfs has no fsck -- any fsck.xfs should be a stub which (hopefully) does nothing or symlinks to /bin/true. Also, notice that after the failure, it say "ignoring error", because /sbin/fsck continues to look through the rest of your PATH for more fsck binaries.

I don't really think there's anything to fix here, unless you'd like to ask util-linux upstream to hide the ENOENT error.
Comment by Shixin Zeng (szeng) - Tuesday, 11 April 2017, 20:16 GMT
So you're saying that "systemd-fsck[160]: fsck: /usr/local/sbin/fsck.xfs: execute failed: No such file or directory" comes from util-linux? But still it's looking for the file 'fsck.xfs' in the wrong directory, could this be a packaging issue?
Comment by Shixin Zeng (szeng) - Wednesday, 12 April 2017, 13:23 GMT
--deleted

Sorry for reposting
Comment by Eric Wang (enihcam) - Thursday, 15 June 2017, 04:03 GMT
Same issue for fsck.btrfs:

systemd-fsck[177]: fsck: /usr/local/sbin/fsck.btrfs: execute failed: No such file or directory

Loading...