On Sun, Mar 15, 2015 at 8:08 PM, Zbigniew Jędrzejewski-Szmek <[email protected]> wrote: > On Sun, Mar 15, 2015 at 07:58:35PM +0100, Kay Sievers wrote: >> If the filesytem is too dumb to have that info in the superblock flags >> to store, to request a forced fsck, it is the problem of the file >> system to fix and nothing we need to solve in systemd. > Are there filesystems which have such a flag?
Some have the "not cleanly unmounted" flag, or mount counters for regular checks. I don't know any details. Maybe this flag or counter could be mis-used to force such a check. In any case, the superblock and corresponding fsck tool would be the right place to put such a force check flag/logic, the info would be stored locally with the actual filesystem, but would not require a r/w mount to place that information. Working around such missing basic filesystem features in systemd code does not sound like the right approach. Kay _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
