Bug 148957

Summary: yast lvm_config does not see all volumes (particular volume name)
Product: [openSUSE] SUSE Linux 10.1 Reporter: First Name Last Name <sinderbox+novell>
Component: YaST2Assignee: Thomas Fehr <fehr>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Beta 4   
Target Milestone: RC 1   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log

Description First Name Last Name 2006-02-08 00:55:18 UTC 
SYMPTOM
#######

I have a lv named 
root--10.1 that belongs to the vg s10

Funny name with double "-", it was created with yast@opensuse10.0 
It is probably another bug, since in the yast dialog 
root-10.1 was used. And it is now the mother of the problem

I can see (in yast) all other lv's in the vg except for this one.

PROBLEM
#######

from y2log:

INFO  libstorage - LvmVg.cc(addLv):631 addLv:root-10.1
[...]
INFO  libstorage - SystemCmd.cc(execute):97 SystemCmd Executing:"dmsetup table "s10-root-10.1""
INFO  libstorage - SystemCmd.cc(addLine):562 Adding Line 1 "device-mapper: table ioctl failed: No such device or address"

from command line:

server:~ # dmsetup table "s10-root-10.1"
device-mapper: table ioctl failed: No such device or address
Command failed
server:~ # dmsetup table "s10-root--10.1"
0 2097152 linear 3:4 471966080

server:~ # lvscan
[...]
ACTIVE            '/dev/s10/root-10.1' [1.00 GB] inherit

server:~ # l /dev/mapper/*10.1*
brw------- 1 root root 253, 13 Feb  7 23:09 /dev/mapper/s10-root--10.1

server:~ # l /dev/s10/*10.1*
lrwxrwxrwx 1 root root 26 Feb  7 23:09 /dev/s10/root-10.1 -> /dev/mapper/s10-root--10.1

server:~ # lvdisplay
[..]
  --- Logical volume ---
  LV Name                /dev/s10/root-10.1

Attached goes the y2log, but I think the problem is clear.
Comment 1 First Name Last Name 2006-02-08 00:59:52 UTC 
Created attachment 66911 [details]
y2log
Comment 2 Thomas Fehr 2006-02-08 13:49:50 UTC 
Using dashes in LV names is prone to lead into problems.
If possible simply dont use dashes in LV names.
W
Comment 3 First Name Last Name 2006-02-08 14:21:46 UTC 
At creation time I saw the dash doubling.
Was not sure if it was caused by LVM or YaST

After that, I did not encounter any LVM problem. But when decided to delete it just in case, realized it is invisible within YaST. (I strongly believe however former YaST versions DID see the LV)

Of course I can do it from the command line.
I will leave it there until I am not further info/testing required.
Comment 4 Thomas Fehr 2006-02-08 15:01:01 UTC 
The dash doubling happens internally by LVM since the naming scheme of
LVM LVs in device-mapper uses the single dash for certain special cases
(e.g. as delimiter between vg name and lv name). 

Probably the invisibility in YaST2 is caused by the mismatch between dm 
name (s10-root--10.1) and lv name (root-10.1).
Comment 5 First Name Last Name 2006-02-08 15:13:03 UTC 
Yes, check the three Y2log lines I posted above.

YaST runs 
dmsetup table "s10-root-10.1"
and fails.

it should run 
dmsetup table "s10-root--10.1"
0 2097152 linear 3:4 471966080
which works

Shouldn't it?
Now I am getting confuse
the LV is called s10-root-10.1
but its mapping in the filesystem is
/dev/mapper/s10-root--10.1

Its a YaST or dmsetup bug?
Comment 6 Thomas Fehr 2006-02-08 15:21:01 UTC 
Of course it is a YaST bug.
dmsetup does not in any way care about the names of its tables.
Comment 7 Thomas Fehr 2006-03-14 19:08:49 UTC 
*** Bug 153573 has been marked as a duplicate of this bug. ***
Comment 8 Thomas Fehr 2006-03-22 17:57:19 UTC 
problem should be fixed in RC1