Control: severity -1 important
Hi,
On Thu, May 18, 2017 at 10:32:02AM +0200, Christoph Biedl wrote:
> Michael Biebl wrote...
>
> > To mark as mountpoint as network mount, there is the _netdev mount
> > option.
>
> While I can confirm this provides a sane and safe shutdown for a mounted
>
Am 18.05.2017 um 10:32 schrieb Christoph Biedl:
> Michael Biebl wrote...
>
>> To mark as mountpoint as network mount, there is the _netdev mount
>> option.
>
> While I can confirm this provides a sane and safe shutdown for a mounted
> AoE-device, this works only if the device was initially
Michael Biebl wrote...
> To mark as mountpoint as network mount, there is the _netdev mount
> option.
While I can confirm this provides a sane and safe shutdown for a mounted
AoE-device, this works only if the device was initially mounted using
that extra option. A later "mount -o
Am 14.05.2017 um 11:36 schrieb Guus Sliepen:
> Another option is to explicitly add a dependency on the network for a
> given mount point in /etc/fstab, see the systemd.mount manpage.
> Basically, the following should work:
>
> /dev/etherd/... /mountpoint ext4
On Sun, May 14, 2017 at 12:49:12PM +0200, Christoph Biedl wrote:
> > Maybe this bug should be reassigned to aoetools to provide a
> > proper systemd.service file?
>
> Wearing the aoetools maintainer's hat, I'll be happy to provide that but
> will need help on it.
Ok. I'll try to create one and
Guus Sliepen wrote...
> I understand the gravity of this bug, the problem is that it's not
> ifupdown's fault. That it was ifupdown itself that kept a network
> interface up when it detected a network filesystem still being mounted
> was a *hack*.
Agreed, but at least it worked quite well for
Hello Biedl & Biebl,
> > retitle 857573 No longer umounts AoE/NBD-based file systems, causing data
> > loss
> Bug #857573 [ifupdown] systemd: Raise network interfaces fails to stop
> cleanly on shutdown/reboot
> Changed Bug title to 'No longer umounts AoE/NBD-based file systems, causing
> data
7 matches
Mail list logo
