Bug 195476 - [RHEL4 U4 beta] anaconda stalls when executes 'lvm vgchange -ay' if the system has some mirror LVs in one VG. (Regression)
Summary: [RHEL4 U4 beta] anaconda stalls when executes 'lvm vgchange -ay' if the syste...
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Alasdair Kergon
QA Contact:
Keywords: Regression
Depends On: 193604
Blocks: 181411
TreeView+ depends on / blocked
Reported: 2006-06-15 13:23 UTC by Jeff Layton
Modified: 2014-06-18 07:35 UTC (History)
9 users (show)

Clone Of:
Last Closed: 2006-08-10 21:49:55 UTC

Attachments (Terms of Use)
proposed patch (1.99 KB, patch)
2006-06-15 14:34 UTC, Jeff Layton
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0504 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2006-08-10 04:00:00 UTC

Comment 1 Jeff Layton 2006-06-15 13:27:59 UTC
To summarize:

Whether Jonathan's patch goes in or not, we'll end up with the event monitoring
daemon not getting started at boot time. So we need to activate it later
(sometime after /usr is mounted). This BZ is opened to make that happen.

Since we're doing that, I'll also change the lvm.static vgchange to prevent it
from trying to start the monitoring too and circumvent the error messages.

Comment 2 Bill Nottingham 2006-06-15 14:16:17 UTC
Wait, why is the command *now* starting a daemon on LVM activation?

That should be done either a) via udev rules or b) via a separate initscript. I
don't see how --monitor yes should ever be the default.

Comment 3 Jeff Layton 2006-06-15 14:34:35 UTC
Created attachment 130978 [details]
proposed patch

This patch adds "--monitor n" to the initscripts, though Bill's suggestion to
make that the default may be a better way to go.

...actually, I seem to now be getting different results when using "--monitor
n". After a fresh reboot, with this patch:

[root@x330-2 ~]# vgchange -an
  testvg-lv1: event deregistration failed: No such device
  testvg-lv2: event deregistration failed: No such device
  0 logical volume(s) in volume group "testvg" now active
[root@x330-2 ~]# vgchange -an --monitor n
  0 logical volume(s) in volume group "testvg" now active
[root@x330-2 ~]# vgchange --monitor n
[root@x330-2 ~]# vgchange -ay
[root@x330-2 ~]# lvm.static vgchange -ay --monitor n
  2 logical volume(s) in volume group "testvg" now active
[root@x330-2 ~]# lvm.static vgchange -ay --monitor n
  testvg-lv1: event deregistration failed: No such device
  Failed to unregister logical volume, lv1
<hang here>

So now I'm not so sure that "--monitor n" is actually helping here.

Comment 4 Jonathan Earl Brassow 2006-06-15 20:45:39 UTC
Firstly, when the dmeventd patch goes in, it should _not_ hang.  At which point,
this may turn into an LVM bug.  It is confusing whether the '--monitor n' in the
last two commands means "don't perform any monitoring ops" or "unmonitor all
devices".  Seems to me it is the latter.

The '[root@x330-2 ~]# vgchange -ay' loaded and monitored the devices.
The following '[root@x330-2 ~]# lvm.static vgchange -ay --monitor n' are
unmonitorring them...

I'll test this more and see what bugs exist with the upcomming code.

Comment 8 Alasdair Kergon 2006-07-04 20:27:37 UTC
Some fixes and workarounds added to 2.02.06-4.0 to address several of the
problems mentioned on this bug.

Comment 11 Red Hat Bugzilla 2006-08-10 21:49:56 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.