Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 906963

Summary:	mount.py Failed to parse /dev/VGNAME/LVNAME format
Product:	[Retired] oVirt	Reporter:	Pavel Zhukov <pzhukov>
Component:	vdsm	Assignee:	Nir Soffer <nsoffer>
Status:	CLOSED DUPLICATE	QA Contact:	Haim <hateya>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2	CC:	abaron, acathrow, amureini, bazulay, ewarszaw, iheim, jkt, mgoldboi, nobody, pzhukov, yeylon
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-29 09:12:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Zhukov 2013-02-02 02:32:31 UTC

Description of problem:
vdsm can't grep local devices mounted by /dev/VG/LV instead /dev/mapper/VG_LV because there are /proc/mount contains only /dev/mapper  records

Version-Release number of selected component (if applicable):
vdsm-4.10.3-6.fc18.x86_64

How reproducible:
100%

Steps to Reproduce:
1. create LVM
2. make FS
3. try to use it as storage domain
  
Actual results:
OSError: [Errno 2] Mount of `/dev/vms/ovirt_master` at `/rhev/data-center/mnt/_dev_vms_ovirt__master` does not exist

Additional info:

Comment 1 Dan Yasny 2013-02-02 14:59:28 UTC

This is about POSIX-FS, not local storage domains. IMO this is a doc bug that the guides don't mention having to go through /dev/mapper/vg-lv as it makes sense to use the dm abstraction for all devices

Comment 2 Ayal Baron 2013-02-03 15:59:56 UTC

(In reply to comment #1)
> This is about POSIX-FS, not local storage domains. IMO this is a doc bug
> that the guides don't mention having to go through /dev/mapper/vg-lv as it
> makes sense to use the dm abstraction for all devices

Are you saying that it doesn't work with posix but does work with local?
How is this a doc issue? vdsm should be agnostic to the underlying storage.
With local storage just needs a file system
With posix, just need an fs type to mount

Comment 3 Pavel Zhukov 2013-02-03 20:44:59 UTC

Sorry for confusing in the description. 

If a posixfs is added using /dev/VGNAME/LVNAME path (instead of /dev/mapper/VGNAME_LVNAME) vdsm can mount it but cannot vefify if FS mounted

For example I tried to add /dev/vms/ovirt_master with VFS ext4 and got error "mount not found" because: 

def _iterKnownMounts():
    with open("/proc/mounts", "r") as f:
        for line in f:
            yield _parseFstabLine(line)

but /proc/mounts contains /dev/mapper/vms/ovirt_master instead of /dev/vms/ovirt_master

Comment 4 Eduardo Warszawski 2013-06-09 11:32:48 UTC

You should use the mounted FS as a localSD.

Related to: BZ#891074.

Comment 5 Pavel Zhukov 2013-06-10 06:22:36 UTC

Eduardo, 
This is about Phttps://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.2-Beta/html-single/Installation_Guide/index.html#sect-Adding_POSIX_Compliant_File_System_StorageOSIX-FS, not local storage domains

Please see #2.

Comment 6 Allon Mureinik 2013-11-07 13:04:14 UTC

(In reply to Pavel Zhukov from comment #5)
> Eduardo, 
> This is about
> Phttps://access.redhat.com/site/documentation/en-US/
> Red_Hat_Enterprise_Virtualization/3.2-Beta/html-single/Installation_Guide/
> index.html#sect-Adding_POSIX_Compliant_File_System_StorageOSIX-FS, not local
> storage domains
> 
> Please see #2.
The link seems to be broken. Can you paste the relevant content here?

Comment 7 Ayal Baron 2013-12-29 09:12:30 UTC


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