Re: [f2fs-dev] Possible issues with fsck of f2fs root
Brought to you by:
kjgkr
From: Norbert L. <nol...@gm...> - 2020-07-24 08:11:49
|
Hello, I ran into this problem with fsck.f2fs 1.13.0, it seems that problem is not fixed in master either. My setup is an embedded device with systemd and I did nothing but swap the filesystem from ext4 to f2fs. The result was that the init system would try to fsck the ro mounted root partition, fsck.f2fs would fail (as noted), and the init system would reboot (rinse, repeat) with no real chance to interact remotely (headless system). Thats pretty much as bad as it gets for an unwanted sideffect ;) I first reported it to systemd, quite reasonably they expect fsck tools to behave the same [1]. The systemd-fsck tool will end up calling fsck.f2fs with the parameter below, and will fail as this device is mounted (tries to open it in exclusive mode). $ fsck.f2fs -a /dev/mmcblk0p5; echo $? Info: Fix the reported corruption. Info: Mounted device! Info: Check FS only on RO mounted device Error: Failed to open the device! 255 A workaround would be to force or skip the check fsck.f2fs -a -f /dev/mmcblk0p5; echo $? Info: Fix the reported corruption. ..... Done: 0.232165 secs 0 So, Id consider this a critical issue, and I dont see whats the conclusion of this discussion is. Norbert [1] - https://github.com/systemd/systemd/issues/15106 |