[systemd-devel] remote-fs ordering, iSCSI and _netdev

[Ivan Shapovalov]

On Tuesday 28 October 2014 at 06:41:32, Andrei Borzenkov wrote:	
> В Mon, 27 Oct 2014 14:10:47 -0700
> Chris Leech <cleech at redhat.com> пишет:
> 
> > 
> > At boot fstab-generator is picking up on the _netdev option in fstab,
> > and the generated mount units are ordered against remote-fs properly.
> > If I leave a filesystem mounted at shutdown, it will be unmounted before
> > the iSCSI session is destroyed or the network is shut down and
> > everything works as expected.
> > 
> > But there are two cases that are problematic, adding entries to fstab at
> > runtime and manually mounting without adding to fstab (while still using
> > the _netdev option, some hint is needed).  The first case actually ends
> > up being the second, with the possible work-around of always remembering
> > to run a daemon-reload after editing fstab to run fstab-generator again.
> >
> 
> Even known network filesystems still have a problem. If network
> filesystem is mounted on boot, it pulls in network-online.target which
> (hopefully) serves as synchronization point on shutdown. If there is no
> network filesystem to mount at boot, network-online.target is not
> started. If you mount NFS manually later there is nothing to wait for
> on shutdown so network could be teared down before filesystem is
> unmounted.

Isn't this (unmount before teardown) achieved by After=network.target? That
target is passive, so it is pulled in by a provider, and all should work
even in case of manually mounted filesystems.

Am I wrong somewhere?

-- 
Ivan Shapovalov / intelfx /
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20141109/ec4b9885/attachment.sig>