[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#863282: marked as done (release-notes: Recommend the _netdev mount option for AoE (ATA over ethernet) devices)

Your message dated Mon, 05 Jun 2017 09:13:00 +0000
with message-id <338c420c-710c-cb7e-3b2e-be9814259539@thykier.net>
and subject line Re: release-notes: Recommend the _netdev mount option for AoE (ATA over ethernet) devices
has caused the Debian Bug report #863282,
regarding release-notes: Recommend the _netdev mount option for AoE (ATA over ethernet) devices
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
863282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863282
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal

Hello,

on systemd-based installations, there is a change in stretch how a mount
using an AoE (ATA over ethernet) device is handled during shutdown,
likewise for swap over AoE: The scripts provided by ifupdown no longer
detect such a situation, and therefore no longer skip network
deconfiguration then. This is tracked as #862530.

However, there's a solution by providing an additional mount option
"_netdev". Then, systemd will handle the situation in a sensible way.

Therefore, I'd like to add a recommendation to the release notes,
basically as follows:

=======================================================================

# The _netdev mount option is recommended when using AoE (ATA over ethernet) devices

Due to a cleanup in the handling of network deconfiguration, AoE devices
in use are no longer handled as expected during shutdown, possibly
resulting in hangs and/or data loss. To migigate that situation, it is
suggested to mount such devices using the "_netdev" mount option. That
option is available when using swap over AoE as well.

=======================================================================

Feel free to re-word or ask for clarification. I will also lower the
severity of the bug mentioned above, since all other scenarios were not
supported in jessie, so there is no regression.

Aside: It seems this trick does not work for NBD (#862531), I'm still
testing. Also, usage of iSCSI devices might be affected.

Regards,
    Christoph

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Wed, 24 May 2017 22:43:38 +0200 Christoph Biedl
<debian.axhn@manchmal.in-ulm.de> wrote:
> Package: release-notes
> Severity: normal
> 
> Hello,
> 
> on systemd-based installations, there is a change in stretch how a mount
> using an AoE (ATA over ethernet) device is handled during shutdown,
> likewise for swap over AoE: The scripts provided by ifupdown no longer
> detect such a situation, and therefore no longer skip network
> deconfiguration then. This is tracked as #862530.
> 
> However, there's a solution by providing an additional mount option
> "_netdev". Then, systemd will handle the situation in a sensible way.
> 
> Therefore, I'd like to add a recommendation to the release notes,
> basically as follows:
> 
> =======================================================================
> 
> # The _netdev mount option is recommended when using AoE (ATA over ethernet) devices
> 
> Due to a cleanup in the handling of network deconfiguration, AoE devices
> in use are no longer handled as expected during shutdown, possibly
> resulting in hangs and/or data loss. To migigate that situation, it is
> suggested to mount such devices using the "_netdev" mount option. That
> option is available when using swap over AoE as well.
> 
> =======================================================================
> 
> Feel free to re-word or ask for clarification. I will also lower the
> severity of the bug mentioned above, since all other scenarios were not
> supported in jessie, so there is no regression.
> 
> Aside: It seems this trick does not work for NBD (#862531), I'm still
> testing. Also, usage of iSCSI devices might be affected.
> 
> Regards,
>     Christoph

Thanks.

I have added the text and it will be live in a few hours from now.

~Niels

--- End Message ---
Reply to: