[systemd-devel] network and remote-fs on shutdown

[Zbigniew Jędrzejewski-Szmek]

On Tue, Sep 11, 2012 at 03:03:31PM +0200, Lennart Poettering wrote:
> On Tue, 11.09.12 14:14, Michel Lafon-Puyo (michel.lafonpuyo at gmail.com) wrote:
> 
> Heya,
> 
> > So the simplified dependency graph I obtain is:
> > 
> > remote-fs-pre.target   mnt-be.automount
> >         \                  /      |
> >          \                /       |
> >           \              /        |
> >            \            /         |
> >             \          /          |
> >             mnt-be.mount          |
> >                                   |
> >                                   |
> >                               remote-fs
> >                                   |
> >                                   |
> >                                   |
> >                         systemd-user-sessions
> > 
> > 
> > 
> > As I understand it, there is no boot-up order between
> > systemd-user-sessions and mnt-be.mount so on shutdown there is a
> > race condition between systemd-user-sessions and mnt-be.mount.
> > 
> > Is it right?
> 
> Yes, this seems right.
> 
> Now, the question is what to do about it... I really have no nice way
> out here short of biting the bullet and adding the ability of allowing
> configuration of shutdown ordering that is not just the inverse of the
> startup ordering. Then we could still allow the mount to be unordered
> against remote-fs at startup but order it at shutdown.
> 
> Hmm, Michal, Kay, do you guys have any suggestions what we could do here?

What about retrying the unmounting after a delay if EBUSY is encountered?
sysvinit scripts seem to do that usually.

Zbyszek