Bug 808655 - [oVir][vdsm]storage create issue: LOCALFS, sometimes hang on storage.sdc.refreshStorage()
Summary: [oVir][vdsm]storage create issue: LOCALFS, sometimes hang on storage.sdc.refr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.3.4
Assignee: wenchao xia
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-31 03:24 UTC by wenchao xia
Modified: 2016-02-10 16:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-12 09:37:33 UTC
oVirt Team: Storage


Attachments (Terms of Use)
test script to reproduce it, unzip it and run exe_test.sh (1.48 KB, application/gzipped-tar)
2012-03-31 03:24 UTC, wenchao xia
no flags Details
logs when the call hangs (8.51 KB, text/plain)
2012-03-31 03:26 UTC, wenchao xia
no flags Details

Description wenchao xia 2012-03-31 03:24:44 UTC
Created attachment 574124 [details]
test script to reproduce it, unzip it and run exe_test.sh

Description of problem:
    when createStorageDomain is called with a LOCALFS, sometimes it hang on at the step of refreshStorage() and never return.

Version-Release number of selected component (if applicable):
vdsm-cli-4.9.6-0.53.gitd4a0516.fc16.noarch
vdsm-4.9.6-0.53.gitd4a0516.fc16.x86_64
vdsm-python-4.9.6-0.53.gitd4a0516.fc16.noarch


How reproducible:
    often but not every time.

Steps to Reproduce:
1. restart vdsmd
2. connect storageServer with LOCALFS
3. create storageDomain
  
Actual results:
    step 3 sometime hang on

Expected results:
    it should return a result.

Additional info:
    There is somtimes another error tips "permission deny" in this case, I will fire it in another bug.

Comment 1 wenchao xia 2012-03-31 03:26:24 UTC
Created attachment 574125 [details]
logs when the call hangs

this is the log.

Comment 2 Itamar Heim 2013-03-12 09:37:33 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.