Bug 215977
| Summary: | a forced pvremove of pvs with pvmoves inprogress will hang | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | agk, dwysocha, jbrassow, mbroz, prockai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2007-0287 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-05-08 00:13:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Corey Marthaler
2006-11-16 17:41:45 UTC
Can you attach a full -vvvv from the hanging pvremove command? And there are *no* other lvm processes running at the time (as you killed the pvmove process)? [root@link-08 ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda1 vg lvm2 a- 135.66G 125.68G
/dev/sdb1 vg lvm2 a- 135.66G 125.68G
/dev/sdc1 vg lvm2 a- 135.66G 135.66G
/dev/sdd1 vg lvm2 a- 135.66G 135.66G
/dev/sde1 vg lvm2 a- 135.66G 135.66G
/dev/sdf1 vg lvm2 a- 135.66G 135.66G
/dev/sdg1 vg lvm2 a- 135.66G 135.66G
[root@link-08 ~]# lvs -a -o +devices
LV VG Attr LSize Origin Snap% Move Log Copy% Devices
segment0 vg -wi-a- 9.98G /dev/sda1(0)
segment1 vg -wi-a- 9.98G /dev/sdb1(0)
[root@link-08 ~]# pvmove /dev/sda1
/dev/sda1: Moved: 2.8%
/dev/sda1: Moved: 5.8%
/dev/sda1: Moved: 8.8%
[^C]
[root@link-08 ~]# ps -ef | grep pvmove
root 4084 3944 0 09:16 pts/0 00:00:00 grep pvmove
[root@link-08 ~]# pvremove -vvvv -ff /dev/sd[abcdefg]1
[...]
#metadata/pv_manip.c:241 /dev/sda1 0: 0 2555: pvmove0(0:0)
#metadata/pv_manip.c:241 /dev/sda1 1: 2555 32173: NULL(0:0)
#metadata/pv_manip.c:241 /dev/sdb1 0: 0 2555: segment1(0:0)
#metadata/pv_manip.c:241 /dev/sdb1 1: 2555 32173: NULL(0:0)
#metadata/pv_manip.c:241 /dev/sdc1 0: 0 2555: pvmove0(0:1)
#metadata/pv_manip.c:241 /dev/sdc1 1: 2555 32173: NULL(0:0)
#metadata/pv_manip.c:241 /dev/sdd1 0: 0 34728: NULL(0:0)
#metadata/pv_manip.c:241 /dev/sde1 0: 0 34728: NULL(0:0)
#metadata/pv_manip.c:241 /dev/sdf1 0: 0 34728: NULL(0:0)
#metadata/pv_manip.c:241 /dev/sdg1 0: 0 34728: NULL(0:0)
Really WIPE LABELS from physical volume "/dev/sda1" of volume group "vg" [y/n]? y
WARNING: Wiping physical volume label from /dev/sda1 of volume group "vg"
#device/dev-io.c:393 /dev/sda1: open failed: Device or resource busy
#pvremove.c:96 Can't open /dev/sda1 exclusively. Mounted filesystem?
#locking/file_locking.c:164 Locking /var/lock/lvm/P_orphans WB
#locking/file_locking.c:111 CTRL-c detected: giving up waiting for lock
#locking/file_locking.c:187 /var/lock/lvm/P_orphans: flock failed: Interrupted
system call
#pvremove.c:81 Can't get lock for orphan PVs
#locking/file_locking.c:164 Locking /var/lock/lvm/P_orphans WB
#locking/file_locking.c:111 CTRL-c detected: giving up waiting for lock
#locking/file_locking.c:187 /var/lock/lvm/P_orphans: flock failed: Interrupted
system call
#pvremove.c:81 Can't get lock for orphan PVs
#locking/file_locking.c:164 Locking /var/lock/lvm/P_orphans WB
[HANG]
It will hang unless I hit ^C 7 times (I assume because that's the number of pvs
that I'm attempting to remove).
fix applied upstream for 2.02.15 This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. 2.02.15-3 fix verified in lvm2-2.02.15-3 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. http://rhn.redhat.com/errata/RHBA-2007-0287.html |