Bug 639114 - deadlock while running pvmove on segmented volume.
Summary: deadlock while running pvmove on segmented volume.
Keywords:
Status: CLOSED DUPLICATE of bug 566799
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cmirror
Version: 5.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jonathan Earl Brassow
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-30 21:03 UTC by Corey Marthaler
Modified: 2010-11-24 14:19 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-12 17:00:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Marthaler 2010-09-30 21:03:46 UTC
Description of problem:
This was the 10th iteration of this test so this certainly doesn't happen every time.

./mirror_sanity -l /home/msp/cmarthal/work/rhel5/sts-root -r /usr/tests/sts-rhel5.5 -R ../../var/share/resource_files/taft.xml -e segmented_pvmove

SCENARIO - [segmented_pvmove]
Create a couple small segmented lvs and then pvmove them
Running lv_seg on taft-02 to create the segmented volumes
taft-02: /usr/tests/sts-rhel5.5/lvm2/bin/lv_seg -v mirror_sanity -n segment
Deactivating segment0 mirror
Moving data from pv /dev/sdc1
taft-02: pvmove -v /dev/sdc1
    Finding volume group "mirror_sanity"
    Executing: /sbin/modprobe dm-log-clustered 
    Archiving volume group "mirror_sanity" metadata (seqno 53).
    Creating logical volume pvmove0
    Moving 273 extents of logical volume mirror_sanity/segment0
    Moving 219 extents of logical volume mirror_sanity/segment1
    Updating volume group metadata
    Creating volume group backup "/etc/lvm/backup/mirror_sanity" (seqno 54).
    Checking progress before waiting every 15 seconds
    Updating volume group metadata
    Creating volume group backup "/etc/lvm/backup/mirror_sanity" (seqno 55).
    Updating volume group metadata

    [DEADLOCK]

taft-02:
Sep 30 00:42:18 taft-02 clogd[32041]: [RMaILehL] Failed to open checkpoint: SA_AIS_ERR_NOT_EXIST
Sep 30 00:42:18 taft-02 clogd[32041]: [RMaILehL] Reinitializing checkpoint library handle
Sep 30 00:42:18 taft-02 clogd[32041]: [RMaILehL] Failed to open checkpoint: SA_AIS_ERR_NOT_EXIST
Sep 30 00:42:18 taft-02 clogd[32041]: [RMaILehL] Reinitializing checkpoint library handle
[...]

taft-03:
Sep 30 00:42:15 taft-03 kernel: device-mapper: dm-log-clustered: [RMaILehL] Request timed out: [DM_CLOG_RESUME/15182174] - retrying
Sep 30 00:42:30 taft-03 kernel: device-mapper: dm-log-clustered: [RMaILehL] Request timed out: [DM_CLOG_RESUME/15182175] - retrying
Sep 30 00:42:45 taft-03 kernel: device-mapper: dm-log-clustered: [RMaILehL] Request timed out: [DM_CLOG_RESUME/15182176] - retrying
Sep 30 00:43:00 taft-03 kernel: device-mapper: dm-log-clustered: [RMaILehL] Request timed out: [DM_CLOG_RESUME/15182177] - retrying
[...]



Version-Release number of selected component (if applicable):
2.6.18-194.11.3.el5

lvm2-2.02.73-2.el5    BUILT: Mon Aug 30 06:36:20 CDT 2010
lvm2-cluster-2.02.73-2.el5    BUILT: Mon Aug 30 06:38:05 CDT 2010
device-mapper-1.02.54-2.el5    BUILT: Fri Sep 10 12:00:05 CDT 2010
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009


How reproducible:
Once so far

Comment 1 Nate Straz 2010-11-12 17:00:46 UTC
Log messages look exactly like 566799.

*** This bug has been marked as a duplicate of bug 566799 ***


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