Hello, This is the error i see in vdsm.log Any pointers appreciated.
Thread-237764::INFO::2012-02-21 22:04:52,785::logUtils::37::dispatcher::(wrapper) Run and protect: createVG(vgname='2b63c813-6bd5-4488-904c-dba1c8e52822', devlist=['3600a0b800017dd4f00000e2e4a4ab484'], options=None) Thread-237764::DEBUG::2012-02-21 22:04:52,788::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvcreate --config " devices { preferred_names = [\"^/dev/mapper/\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \"a%3600a0b800017dcec00000f324a4ab9ef|3600a0b800017dcec00000f334a4aba67|3600a0b800017dcec00000f344a4aba75|3600a0b800017dcec00000f354a4aba8d|3600a0b800017dd4f00000e2e4a4ab484|3600a0b800017dd4f00000e2f4a4ab56c%\", \"r%.*%\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --metadatasize 128m --metadatacopies 2 --metadataignore y /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484' (cwd None) Thread-237764::DEBUG::2012-02-21 22:04:52,854::lvm::287::Storage.Misc.excCmd::(cmd) FAILED: <err> = " Can't open /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484 exclusively. Mounted filesystem?\n"; <rc> = 5 Thread-237764::DEBUG::2012-02-21 22:04:52,857::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvs --config " devices { preferred_names = [\"^/dev/mapper/\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \"a%3600a0b800017dcec00000f324a4ab9ef|3600a0b800017dcec00000f334a4aba67|3600a0b800017dcec00000f344a4aba75|3600a0b800017dcec00000f354a4aba8d|3600a0b800017dd4f00000e2e4a4ab484|3600a0b800017dd4f00000e2f4a4ab56c%\", \"r%.*%\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " -o vg_name,pv_name --noheading /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484' (cwd None) Thread-237764::DEBUG::2012-02-21 22:04:52,914::lvm::287::Storage.Misc.excCmd::(cmd) FAILED: <err> = ' No physical volume label read from /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484\n Failed to read physical volume "/dev/mapper/3600a0b800017dd4f00000e2e4a4ab484"\n'; <rc> = 5 Thread-237764::ERROR::2012-02-21 22:04:52,916::task::855::TaskManager.Task::(_setError) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 863, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 38, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1556, in createVG metadataSize=blockSD.VG_METADATASIZE) File "/usr/share/vdsm/storage/lvm.py", line 796, in createVG _initpvs(pvs, metadataSize) File "/usr/share/vdsm/storage/lvm.py", line 634, in _initpvs found, notFound) PhysDevInitializationError: Failed to initialize physical device: ('found: %s notFound: %s', {}, <generator object <genexpr> at 0x7fd8c031a780>) Thread-237764::DEBUG::2012-02-21 22:04:52,942::task::874::TaskManager.Task::(_run) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Task._run: 17d5267f-fe25-49d4-9a7d-e04f2785d3b7 ('2b63c813-6bd5-4488-904c-dba1c8e52822', ['3600a0b800017dd4f00000e2e4a4ab484']) {} failed - stopping task Thread-237764::DEBUG::2012-02-21 22:04:52,942::task::1201::TaskManager.Task::(stop) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::stopping in state preparing (force False) Thread-237764::DEBUG::2012-02-21 22:04:52,942::task::980::TaskManager.Task::(_decref) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::ref 1 aborting True Thread-237764::INFO::2012-02-21 22:04:52,943::task::1159::TaskManager.Task::(prepare) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::aborting: Task is aborted: 'Failed to initialize physical device' - code 601 Thread-237764::DEBUG::2012-02-21 22:04:52,943::task::1164::TaskManager.Task::(prepare) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Prepare: aborted: Failed to initialize physical device Thread-237764::DEBUG::2012-02-21 22:04:52,943::task::980::TaskManager.Task::(_decref) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::ref 0 aborting True Thread-237764::DEBUG::2012-02-21 22:04:52,943::task::915::TaskManager.Task::(_doAbort) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Task._doAbort: force False
On Tue, Feb 21, 2012 at 04:42:42PM +0530, Deepak C Shetty wrote:
Hello, This is the error i see in vdsm.log Any pointers appreciated.
Thread-237764::INFO::2012-02-21 22:04:52,785::logUtils::37::dispatcher::(wrapper) Run and protect: createVG(vgname='2b63c813-6bd5-4488-904c-dba1c8e52822', devlist=['3600a0b800017dd4f00000e2e4a4ab484'], options=None) Thread-237764::DEBUG::2012-02-21 22:04:52,788::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvcreate --config " devices { preferred_names = [\"^/dev/mapper/\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \"a%3600a0b800017dcec00000f324a4ab9ef|3600a0b800017dcec00000f334a4aba67|3600a0b800017dcec00000f344a4aba75|3600a0b800017dcec00000f354a4aba8d|3600a0b800017dd4f00000e2e4a4ab484|3600a0b800017dd4f00000e2f4a4ab56c%\", \"r%.*%\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --metadatasize 128m --metadatacopies 2 --metadataignore y /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484' (cwd None) Thread-237764::DEBUG::2012-02-21 22:04:52,854::lvm::287::Storage.Misc.excCmd::(cmd) FAILED: <err> = " Can't open /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484 exclusively. Mounted filesystem?\n"; <rc> = 5
Do you have write permission on the /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484 device?
For fibre channel, Vdsm does zero preperations - devices just pop up in the host. Please try `pvcreate /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484` directly from the command line.
Dan.
On 02/21/2012 05:09 PM, Dan Kenigsberg wrote:
On Tue, Feb 21, 2012 at 04:42:42PM +0530, Deepak C Shetty wrote:
Hello, This is the error i see in vdsm.log Any pointers appreciated.
Thread-237764::INFO::2012-02-21 22:04:52,785::logUtils::37::dispatcher::(wrapper) Run and protect: createVG(vgname='2b63c813-6bd5-4488-904c-dba1c8e52822', devlist=['3600a0b800017dd4f00000e2e4a4ab484'], options=None) Thread-237764::DEBUG::2012-02-21 22:04:52,788::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvcreate --config " devices { preferred_names = [\"^/dev/mapper/\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \"a%3600a0b800017dcec00000f324a4ab9ef|3600a0b800017dcec00000f334a4aba67|3600a0b800017dcec00000f344a4aba75|3600a0b800017dcec00000f354a4aba8d|3600a0b800017dd4f00000e2e4a4ab484|3600a0b800017dd4f00000e2f4a4ab56c%\", \"r%.*%\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --metadatasize 128m --metadatacopies 2 --metadataignore y /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484' (cwd None) Thread-237764::DEBUG::2012-02-21 22:04:52,854::lvm::287::Storage.Misc.excCmd::(cmd) FAILED:<err> = " Can't open /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484 exclusively. Mounted filesystem?\n";<rc> = 5
Do you have write permission on the /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484 device?
For fibre channel, Vdsm does zero preperations - devices just pop up in the host. Please try `pvcreate /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484` directly from the command line.
Figured out the issue. The above dm entry in question actually happens to be a multipath pathname, and it had ...484p1 and ...484p2 partitions created beneath it, so pvcreate fails for it.
I had to disable multipath, remove the p1 and p2 partitions, wipe off the partition table entry from ..484 backed blk devices (sdb, sdh) and then OE was able to create a PV, Vg and lv.
Few obs: 1) When i had disabled mpath, i was expecting OE to show 'sdb' and 'sdh' as the fc block devices , but whenever i tried to open 'new storage domain' it probably autoran mpath to setup mpath on my node and always shows me the multipath pathname (...484 in the above case)
2) why should OE (rather vdsm ) should configure mpath if user has disabled it ?
3) When i permanently disabled mpath (using mpathconf --disable), OE did not show any luns on the new storage domain UI. So why does OE/vdsm detect the fc blk devices as in sdb, sdh and allow user to select that to base his/her's block storage upon ?
Dan.
vdsm-devel@lists.fedorahosted.org