On Wed, Feb 14, 2024 at 03:23:45PM +0100, Karel Zak wrote: > On Wed, Feb 14, 2024 at 01:17:46PM +0100, Stanislav Brabec wrote: > > systemd uses its own implementation of fsck with a slightly different > > behavior (e. g. fsck -A checks noauto volumes, systemd-fsck does not). > > systemd calls fsck from util-linux, but a new instance (with -l) for each device. > It would be nice to be more explicit and explain it, because "it has its > own implementation" sounds like fsck from util-linux is completely out > of game :-) > > > +== NOTES > > +*systemd* does not call *fsck -A*, but it has its own implementation > > *systemd-fsck*(8). > > What about: > > systemd does not invoke fsck -A to check all devices; instead, it > calls fsck individually for devices selected based on the logic > implemented in systemd-fsck. I had short discussion about it with Lennart, and he suggested not to document anywhere systemd-fsck as it's private systemd stuff. I have pushed to repository: https://github.com/util-linux/util-linux/commit/9cb7b7671d903573d6c3b9d8112ec13953cdcdc6 Hope it good enough :-) Karel -- Karel Zak <kzak@xxxxxxxxxx> http://karelzak.blogspot.com
