Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionCorey Marthaler
2011-02-18 18:06:10 UTC
Description of problem:
This is for the issue listed in comment #27 of bug 613829. It's currently only been seen once.
Scenario: Kill disk log of synced 2 leg mirror(s)
********* Mirror hash info for this scenario *********
* names: syncd_log_2legs_1
* sync: 1
* leg devices: /dev/sdd1 /dev/sdg1
* log devices: /dev/sdf1
* no MDA devices:
* failpv(s): /dev/sdf1
* failnode(s): taft-01
* additional snap: /dev/sdd1
* leg fault policy: remove
* log fault policy: allocate
******************************************************
Creating mirror(s) on taft-01...
taft-01: lvcreate -m 1 -n syncd_log_2legs_1 -L 600M helter_skelter
/dev/sdd1:0-1000 /dev/sdg1:0-1000 /dev/sdf1:0-150
Creating a snapshot volume of each of the mirrors
Waiting until all mirrors become fully syncd...
0/1 mirror(s) are fully synced: ( 96.83% )
1/1 mirror(s) are fully synced: ( 100.00% )
Creating ext on top of mirror(s) on taft-01...
mke2fs 1.41.12 (17-May-2010)
Mounting mirrored ext filesystems on taft-01...
Writing verification files (checkit) to mirror(s) on...
---- taft-01 ----
Sleeping 10 seconds to get some outsanding EXT I/O locks before the failure
Verifying files (checkit) on mirror(s) on...
---- taft-01 ----
Disabling device sdf on taft-01
[DEADLOCK]
[root@taft-01 ~]# lvs -a -o +devices
[DEADLOCK]
Looks like dmevetd died during this:
Feb 9 16:56:58 taft-01 abrt[6704]: saved core dump of pid 1222
(/sbin/dmeventd) to /var/spool/abrt/ccpp-1297292218-1222.new/coredump (32448512
bytes)
Feb 9 16:56:58 taft-01 abrtd: Directory 'ccpp-1297292218-1222' creation
detected
Feb 9 16:56:58 taft-01 abrtd: Registered Database plugin 'SQLite3'
Feb 9 16:56:58 taft-01 abrtd: New crash /var/spool/abrt/ccpp-1297292218-1222,
processing
2.6.32-94.el6.x86_64
lvm2-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
lvm2-libs-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
lvm2-cluster-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
udev-147-2.31.el6 BUILT: Wed Jan 26 05:39:15 CST 2011
device-mapper-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
device-mapper-libs-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
device-mapper-event-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
device-mapper-event-libs-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
cmirror-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
Comment 3RHEL Program Management
2011-04-04 02:03:52 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Of course the core dump no longer exists on the machine. Meaning this is probably not going to be tracked down unless it can be reproduced. Corey, any chance on repeating the crash? (Or, alternatively, any chance of the core dump being stashed somewhere still, ideally with a matching dmeventd binary? I don't have access to your $HOME, so it may still be there.)
Comment 7RHEL Program Management
2011-10-07 15:55:01 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.