| Summary: | device-mapper: remove ioctl on failed; error when taking snapshot of inactive origin | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.3 | CC: | agk, dwysocha, heinzm, jbrassow, mbroz, msnitzer, prajnoha, prockai, thornber, zkabelac |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.95-3.el6 | Doc Type: | Bug Fix |
| Doc Text: |
No Documentation needed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 15:02:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Corey Marthaler
2012-03-20 20:15:37 UTC
Hmm, this might be caused by the watch udev rule we've added to our 13-dm-disk.rules as part of the rebase. The reason it shows that the ioctl failed and then the operation succeeded despite that is probably the "retry" code that gets activated - we should see that in the debug log, something like: #ioctl/libdm-iface.c:1687 dm remove (253:2) NFT [16384] (*1) #ioctl/libdm-iface.c:1687 dm remove (253:2) NFT [16384] (*2) ... Where the (*X) is the retry number. The retry probably won't be used if using the debug log with the command as this will slow down the process a bit making time for udev to finish fiddling with the dev :) (I'm thinking now whether we should show these messages as errors on retry or just log them in as a debug message only... OR removing the watch rule in RHEL as its gain is not worth the problems it brings). Corey, please try to remove/comment out the OPTIONS+="watch" line in /lib/udev/rules.d/13-dm-disk.rules and see if you can still hit the problem... Oh, but we need the watch rule for the lvmetad in case the PV is created on top of a DM device. Hmmm... (...an alternative to that would be to send the change event ourselves, just by writing "change" to corresponding /sys/block/dm/uevent after we create the PV, so we could probably do without the watch rule) If I comment out the 'OPTIONS+="watch"' line everything works fine. ============================================================ Iteration 50 of 50 started at Wed Mar 21 14:14:42 CDT 2012 ============================================================ SCENARIO - [create_snap_of_inactive_origin] Create a snapshot of an inactive origin Making origin volume lvcreate -L 300M snapper -n origin Deactivating origin/snap volume(s) lvchange -an snapper/origin Creating snap of inactive origin lvcreate -s /dev/snapper/origin -c 32 -n snap_of_inactive -L 100M Activating origin/snap volume(s) lvchange -ay snapper/origin 2>&1 Removing volume snapper/snap_of_inactive Removing origin snapper/origin Actually, pvcreate updates the lvmetad directly so we don't need the watch rule. I'll remove it in next respin as we had cases before where this caused problems in enterprise environment (this will be a RHEL specific patch).
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No Documentation needed.
Fix verified in the latest rpms. 2.6.32-251.el6.x86_64 lvm2-2.02.95-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 lvm2-libs-2.02.95-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 lvm2-cluster-2.02.95-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 udev-147-2.40.el6 BUILT: Fri Sep 23 07:51:13 CDT 2011 device-mapper-1.02.74-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 device-mapper-libs-1.02.74-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 device-mapper-event-1.02.74-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 device-mapper-event-libs-1.02.74-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 cmirror-2.02.95-3.el6 BUILT: Fri Mar 30 09:54:10 CDT 2012 ============================================================ Iteration 10 of 10 started at Wed Apr 4 14:46:52 CDT 2012 ============================================================ SCENARIO - [create_snap_of_inactive_origin] Create a snapshot of an inactive origin Making origin volume lvcreate -L 300M snapper -n origin Deactivating origin/snap volume(s) Creating snap of inactive origin lvcreate -s /dev/snapper/origin -c 32 -n snap_of_inactive -L 100M Activating origin/snap volume(s) Removing volume snapper/snap_of_inactive Removing origin snapper/origin Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0962.html |