Bugzilla – Bug 75966
mount-by-label of devices on LVM doesn't work
Last modified: 2005-09-01 10:47:29 UTC
Installation with UseSSH=1 /boot is ext2 on hda1, LABEL=Linux_boot, mount by label / is reiser on LVM, LABEL=Linux_slash, mount by label /var is reiser on LVM, LABEL=Linux_var, mount by label Installation works fine until first reboot. After that, the installation doesn't continue because /var is not mounted. /var/log/messages is not created, either. Will try to extract y2logs if possible.
Yes, y2logs are needed. Bugreporing Howto (logs): http://www.suse.de/~sh/Bugreporting-faq/index.html#id2518240 Thank you
arvin, fehr: are you able to test/fix this bug without logs, please?
We will try to reproduce this here.
Created attachment 34762 [details] Contents of /var after reboot
Created attachment 34763 [details] Contents of /var before reboot
It seems this is a problem with mount. mount-by-label doesn't work for device-mapper devices. Strangely enough, blkid sees the labels on these devices just fine. Mount-by-UUID also fails for these devices. So it could well be that this is a bug of mount and not yast. blkid output follows: switch:~ # blkid /dev/sda1: LABEL="Linux_boot" UUID="5e0bcc0b-eafc-4546-bd81-b5b1c19ea8ad" TYPE="ext2" /dev/sda5: TYPE="swap" /dev/system/slash: UUID="ba5d89b4-1ef6-4f8e-98f1-8346163c4e6b" LABEL="Linux_slash" TYPE="reiserfs" /dev/system/var: UUID="854ed0b3-5062-49b6-bde4-2f9e02048f4a" LABEL="Linux_var" TYPE="reiserfs" /dev/system/tmp: UUID="1c5ffc21-4aa6-44a9-8a30-4e219a468d28" LABEL="Linux_tmp" TYPE="reiserfs" /dev/system/home: UUID="81e8ed06-7bef-4484-84f1-80d6553d0ed7" LABEL="Linux_home" TYPE="reiserfs" /dev/system/srv: UUID="dc14ee6c-88f9-418a-9243-0214ef81fd32" LABEL="Linux_srv" TYPE="reiserfs" /dev/system/storage: UUID="7334140f-dbe0-429f-a45b-5d8b64827712" LABEL="Linux_storage" TYPE="reiserfs" /dev/mapper/system-slash: UUID="ba5d89b4-1ef6-4f8e-98f1-8346163c4e6b" LABEL="Linux_slash" TYPE="reiserfs" /dev/mapper/system-var: UUID="854ed0b3-5062-49b6-bde4-2f9e02048f4a" LABEL="Linux_var" TYPE="reiserfs" /dev/mapper/system-storage: UUID="7334140f-dbe0-429f-a45b-5d8b64827712" LABEL="Linux_storage" TYPE="reiserfs" /dev/mapper/system-srv: UUID="dc14ee6c-88f9-418a-9243-0214ef81fd32" LABEL="Linux_srv" TYPE="reiserfs" /dev/hdc: TYPE="iso9660" /dev/mapper/system-home: UUID="81e8ed06-7bef-4484-84f1-80d6553d0ed7" LABEL="Linux_home" TYPE="reiserfs" /dev/mapper/system-tmp: UUID="1c5ffc21-4aa6-44a9-8a30-4e219a468d28" LABEL="Linux_tmp" TYPE="reiserfs" switch:~ # mount LABEL="Linux_srv" /srv/ mount: special device LABEL=Linux_srv does not exist switch:~ # mount UUID="dc14ee6c-88f9-418a-9243-0214ef81fd32" /srv/ mount: special device UUID=dc14ee6c-88f9-418a-9243-0214ef81fd32 does not exist
The I reassigne this to maintainer of util-linux so that he can investigate why mount-by-uuid and -label does not work with device-mapper devices.
mount by uuid and mount by label works fine with device mapper devices, otherwise LVM2 wouldn't work.
In a first glance it works here too, but apparently it did not work in the sequence Carl-Daniel posted in comment #6. Since I see no conjunction to YaST in the sequence Carl-Daniel posted, I do not see what I could do with this bug. If you are sure that Carl-Daniel is wrong, please close with INVALID or WORKSFORME.
It's not a mount bug.
Mads, have you actually tested this on a 9.3 box? I tried it on one box, it failed, I reinstalled, it still failed. On another box it failed, too.
Just regular mount by label and mount by uuid on a device mapper device?
Regular mount by label/uuid works just fine. It's only mount by label/uuid of a device mapper device that fails. To convince you that this actually happens, I'll attach a strace of the failing mount.
Created attachment 34787 [details] strace -o out.mount -f mount LABEL="Linux_srv" /srv/
What if you specify mount -L Linux_srv like the manpage suggests?
What's the output of: ls -l /dev/mapper ?
switch:~ # mount -L Linux_srv mount: no such partition found switch:~ # ls -l /dev/mapper/ total 177 drwxr-xr-x 2 root root 296 Apr 15 10:34 . drwxr-xr-x 36 root root 181536 Apr 16 16:54 .. lrwxrwxrwx 1 root root 16 Apr 15 10:34 control -> ../device-mapper brw------- 1 root root 253, 3 Apr 7 02:12 system-home brw------- 1 root root 253, 0 Apr 7 02:12 system-slash brw------- 1 root root 253, 4 Apr 7 02:12 system-srv brw------- 1 root root 253, 5 Apr 7 02:12 system-storage brw------- 1 root root 253, 2 Apr 7 02:12 system-tmp brw------- 1 root root 253, 1 Apr 7 02:12 system-var
mount -L Linux_srv /srv of course
switch:~ # mount -L Linux_srv /srv/ mount: no such partition found
If you look closely at the strace, it seems mount tries to open /dev/dm-[0-5] which don't exist. It should instead try to open /dev/mapper/* or open by major/minor. switch:~ # cat /proc/partitions major minor #blocks name 8 0 156290904 sda 8 1 530113 sda1 8 2 1 sda2 8 5 2104483 sda5 8 6 153645628 sda6 253 0 8388608 dm-0 253 1 4194304 dm-1 253 2 4194304 dm-2 253 3 20971520 dm-3 253 4 4194304 dm-4 253 5 41943040 dm-5
Carl-Daniel, you have the setup and the hardware--is there a chance you can debug this further and maybe narrow it down a bit more?
Quoting from comment #20: "mount tries to open /dev/dm-[0-5] which don't exist. It should instead try to open /dev/mapper/* or open by major/minor." An additional way to solve this problem would be to ask some udev tools what the name of the real device is.
Still happens with 10.0beta4. Suggested fix: mount should try to open the devices /dev/mapper/* instead of /dev/dm-*
Can you try /work/built/mbuild/barry-mmj-49?
The above are 10.0 packages
This fixes it. I tested mount-by-label on LVM and on normal partitions. Both work now.
Submitted for STABLE