[systemd-devel] Dependency loop due to network filesystem and quotacheck; suboptimal loop resolution.
lennart at poettering.net
Wed Mar 16 18:36:43 PDT 2011
On Wed, 09.03.11 17:12, Andrey Borzenkov (arvidjaar at gmail.com) wrote:
> There are two issues in it
> 1. Dependency on quotacheck are added to network filesystem
> This is v19. It could be possible that this is fixed in v20.
No it isn't.
There has been an item on the TODO list regarding this, for quite some
time: we should add those quotacheck deps only for mounts which have
either usrquota or grpquota in the options string. If they don't they
are irrelevant for the quota subsystem and hence shouldn't block it.
(In fact, this should even go one step further: instead of enabling
quotacheck.service via sysinit.target, these mounts should pull it in
> 2. When systemd decides to break the loop it removes - guess, what -
> local-fs.target :) So system comes up without anything mounted (as a
> side effect remount-rootfs.service is not called as well).
> There really should be some notion of "more equal" services/targets.
> It is acceptable to come up without /mnt/cesi mounted, but not with
> completely ruined startup.
Hmm, I wonder if we can add a simple logic here that rathers removes
services than targets. Or something like this. I'd prefer an automatism
here over explicitly configured "importance weighs"... Suggestsions
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel