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
2013-03-14 18:31:27 UTC
Description of problem:
Nenad and I noticed that during mirror device failure testing, we're seeing "raid1" write errors coming from device-mapper. Why would d-m be using the raid1 target in this case?
[root@taft-02 ~]# rm -rf /var/log/messages
[root@taft-02 ~]# service rsyslog restart
./helter_skelter -l /home/msp/cmarthal/work/sts/sts-root -r /usr/tests/sts-rhel6.4 -o taft-02 -e kill_secondary_non_synced_4_legs -i 2
[root@taft-02 ~]# grep raid /var/log/messages
Mar 14 11:39:20 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Mar 14 11:39:20 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Mar 14 11:39:20 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
[...]
Mar 14 11:41:16 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Mar 14 11:41:16 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Mar 14 11:41:16 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Mar 14 11:41:16 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Mar 14 11:41:16 taft-02 kernel: device-mapper: raid1: Write error during recovery (error = 0x1)
Version-Release number of selected component (if applicable):
2.6.32-354.el6.x86_64
lvm2-2.02.98-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
lvm2-libs-2.02.98-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
lvm2-cluster-2.02.98-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
udev-147-2.43.el6 BUILT: Thu Oct 11 05:59:38 CDT 2012
device-mapper-1.02.77-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
device-mapper-libs-1.02.77-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
device-mapper-event-1.02.77-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
device-mapper-event-libs-1.02.77-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
cmirror-2.02.98-9.el6 BUILT: Wed Jan 23 10:06:55 CST 2013
How reproducible:
Everytime
Comment 1Jonathan Earl Brassow
2013-05-16 19:18:13 UTC
DM is not using MD's RAID1 in this case. It is simply the error message that has always come from DM's mirroring.
Was that all, or am I missing something?
Probably won't go changing "raid1" to "mirror" for all the messages in LVM mirroring at this point. (Especially since the device-mapper target's name /is/ dm-raid1.c.)
closing NOTABUG