Bug#809166: networking.service does not prevent ifdown with network file systems

[Guus Sliepen]

On Sun, Dec 27, 2015 at 07:58:06PM +0100, Martin Pitt wrote:

> Package: ifupdown
> Version: 0.8
> 
> /etc/init.d/networking has some functionality to check if the root
> file system or swap are on a network file system, in
> check_network_file_systems() and check_network_swap(). In that case,
> the interfaces are not ifdown'ed during shutdown, so that these
> network file systems can be cleanly unmouted at the very end.
> 
> However, the new networking.service does not do that.  So unmounting
> these network file systems will hang and fail as the interface is
> already down. Root on NFS or even more so iSCSI is rather popular, so
> this is quite an important regression.

Please check if the problem still exists with version 0.8.4. Version 0.8
didn't correctly order itself with respect to network-online.target, but
0.8.4 should have fixed that.

> Perhaps these checks can be put into ifdown itself and be done with
> "ifdown -a"? Then you can still ifdown an individual interface (which
> is usually deliberately done by the admin, even if it means shooting
> yourself into the foot), but it would DTRT when being called by the
> init.d script or the systemd unit. Alternatively this could become a
> new option such as --check-netfs that the init scripts use.

No, I won't put such checks in ifdown itself, it should be fixed now.
And if you manually ifdown an interface that is necessary for a network
mount, you can easily ifup it manually to fix it.

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <guus at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151227/863bf5c2/attachment-0002.sig>