[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1312011.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-02-25T14:04:19+00:00 Peter wrote:

This rule may be problematic:

SUBSYSTEM=="block", KERNEL!="ram*",
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"

The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is
on top of such DM device. It's even more problematic if this is used
with multipath which sets DM_UDEV_DISABLE_OTHER_RULES_FLAG in case we
have a CHANGE event that comes after DM multipath device reload when one
of the paths is down or up (see also bug #1310022).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/0


On 2016-02-25T19:01:04+00:00 Ryan wrote:

(In reply to Peter Rajnoha from comment #0)
> This rule may be problematic:
> 
> SUBSYSTEM=="block", KERNEL!="ram*",
> ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
> 
> The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is on
> top of such DM device. It's even more problematic if this is used with
> multipath which sets DM_UDEV_DISABLE_OTHER_RULES_FLAG in case we have a
> CHANGE event that comes after DM multipath device reload when one of the
> paths is down or up (see also bug #1310022).

Hi Peter. Glad to hear that this has been identified as a problem.
Obviously I wouldn't normally edit /usr/lib/udev/rules.d/*.rules files
(I know changes will be reverted on update of systemd; perhaps it works
like systemd unit files and I could put an override file of the same
name in /etc/udev/rules.d?) but if I comment out that rule in
99-systemd.rules, is it sufficient to run `udevadm control --reload` to
avoid being bitten by this issue?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/1


On 2016-02-26T07:58:08+00:00 Peter wrote:

(In reply to Ryan Sawhill from comment #1)
> Hi Peter. Glad to hear that this has been identified as a problem. Obviously
> I wouldn't normally edit /usr/lib/udev/rules.d/*.rules files (I know changes
> will be reverted on update of systemd; perhaps it works like systemd unit
> files and I could put an override file of the same name in
> /etc/udev/rules.d?) but if I comment out that rule in 99-systemd.rules, is
> it sufficient to run `udevadm control --reload` to avoid being bitten by
> this issue?

Yes, you can comment out that rule for now in
/lib/udev/rules.d/99-systemd.rules and then on next systemd update, this
will be overwritten by the new rules file which will have this removed
officially.

And yes, udevadm control --reload should suffice.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/2


On 2016-02-26T08:19:01+00:00 Peter wrote:

However, I missed one point - we still need to be sure that systemd
doesn't consider the device to be ready on ADD event because on ADD
event, any DM device is still not ready - it needs to be loaded with
teable and then resumed. So the rule should be:

UBSYSTEM=="block", ACTION=="add",
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"

(so it checks against 'ACTION=="add"')

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/3


On 2016-02-26T08:33:36+00:00 Peter wrote:

*** Bug 1300453 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/4


On 2016-02-26T08:38:11+00:00 Peter wrote:

*** Bug 1310022 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/5


On 2016-02-26T14:37:05+00:00 Ryan wrote:

Awesome! So to summarize for anyone following this from home, until new
systemd packages including this fix are shipped, you can protect
yourself from this issue by tweaking that line with sed:

  sed -i '/DM_UDEV_DISABLE_OTHER_RULES_FLAG/s|.*|SUBSYSTEM=="block",
KERNEL!="ram*", ACTION=="add",
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"|'
/usr/lib/udev/rules.d/99-systemd.rules

And reloading the rules:

  udevadm control --reload

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/comments/6

--

[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-21 Thread Matt Schulte
I have run for a bit now and have not seen anymore erroneous unmounts.
I'll call this one fixed and verified.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-13 Thread Martin Pitt
@Matt: it landed in xenial yesterday.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-13 Thread Matt Schulte
Can you comment on when or if this fixed package might be pushed to the
Xenial repos?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-12 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu4

---
systemd (229-4ubuntu4) xenial; urgency=medium

  * 73-special-net-names.rules: Further refine ibmveth naming.

 -- Martin Pitt   Tue, 12 Apr 2016 12:06:30
+0200

** Changed in: systemd (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-11 Thread Martin Pitt
Fix landed upstream, I imported it into our package.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-11 Thread Martin Pitt
Upstreamed: https://github.com/systemd/systemd/pull/3013

** Bug watch added: Red Hat Bugzilla #1312011
   https://bugzilla.redhat.com/show_bug.cgi?id=1312011

** Also affects: systemd (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1312011
   Importance: Unknown
   Status: Unknown

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

2016-04-04 Thread Matt Schulte
This bug is being tracked in Netapp's internal bug tracking system:
LSIP200858428

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs