Bug 751705 - [vdsm] spm start fails due to several processes racing each other
Summary: [vdsm] spm start fails due to several processes racing each other
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.3.4
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-07 08:52 UTC by Haim
Modified: 2016-02-10 17:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-11 21:58:34 UTC
oVirt Team: Storage

Attachments (Terms of Use)
vdsm log (1.30 MB, application/x-gzip)
2011-11-07 08:52 UTC, Haim 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Haim 2011-11-07 08:52:33 UTC 
Created attachment 531990 [details]
vdsm log

Description of problem:

description: 

spmStart process fails due to several spm protect racing each other and trying to acquire same lock over storage domain.
also, master domain remains mounted on /rhev/data-center/ during that process. 

setup: 1 RHEL host, connected to 2 storage domains over iSCSI

flow: activate host - spmStart flow

mitigation: kill all spm protect processes and mount master domain manually.

repo: 

should be available on git://git.fedorahosted.org/vdsm.git

attached vdsm log.
Comment 1 Haim 2012-04-01 12:46:27 UTC 
just hit it again:


  PID TTY      STAT   TIME COMMAND
23261 ?        S<s    0:00 /bin/bash /usr/libexec/vdsm/spmprotect.sh renew 610da315-59ee-4058-ba7e-f81df40bfbad 1 5 /dev/610da315-59ee-4058-ba7e-f81df40bfbad/leases 60000 10000 1333284048563479
27379 ?        S<     0:00 /bin/bash /usr/libexec/vdsm/spmprotect.sh renew 610da315-59ee-4058-ba7e-f81df40bfbad 1 5 /dev/610da315-59ee-4058-ba7e-f81df40bfbad/leases 60000 10000 1333284048563479
Comment 2 Itamar Heim 2013-03-11 21:58:34 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Note You need to log in before you can comment on or make changes to this bug.