Bug 584985

Created attachment 408438 [details]
/etc/fstab

system-config-lvm-1.1.13-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/system-config-lvm-1.1.13-1.fc13

system-config-lvm-1.1.13-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/system-config-lvm-1.1.13-1.fc12

Thanks for reporting bug, I hope it is fixed now

Created attachment 410088 [details]
Screen shot of error "in use but not mounted"

Sorry, but it does not work for me.

The GUI shows both volumes (backup and vm) as unmounted although they are mounted.

When I try to change the size (initial problem task), an error message says that the volume is not mounted but used ...

I tried with the checkbox "mounted" both options as enabled and disabled, it is not checked initially. "Mount on boot" is checked.

@Raphael:

Can you send me '/etc/mtab' and '/proc/mounts' from a situation when it does not work? We parse results from these two files and it is possible that there is something different.

system-config-lvm-1.1.13-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Created attachment 410655 [details]
Content of /etc/mtab and /proc/mounts

(In reply to comment #7)
I reinstalled the package from updates-testing repository and I get the same error as described in comment #5.

(In reply to comment #6)
Marek, please look at the attachment 410655 [details] for /etc/mtab and /proc/mounts.

system-config-lvm-1.1.13-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Created attachment 411705 [details]
Debug patch

@Raphael:

please try to apply this patch and send me an output. I'm not able to reproduce your bug but if I guess correctly than problem should be close to this function.

(In reply to comment #11)
Here comes the output of system-config-lvm to console. 
If the problem is still not reproducable for you, please close this bug. In that case, I will guess a local problem only due to my configuration or something like that ...

paths: ['/dev/vol/backup']
NONE EARLY
paths: ['/dev/vol/vm']
NONE EARLY
paths: ['/dev/vg_spritty/lv_root']
NONE EARLY
paths: ['/dev/vg_spritty/lv_swap']
NONE EARLY
paths: ['/dev/vg_spritty/lv_home']
NONE EARLY
paths: ['/dev/sda1']
LINErootfs / rootfs rw 0 0
LINE/proc /proc proc rw,relatime 0 0
LINE/sys /sys sysfs rw,seclabel,relatime 0 0
LINEudev /dev devtmpfs rw,seclabel,relatime,size=1891664k,nr_inodes=472916,mode=755 0 0
LINEdevpts /dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=000 0 0
LINEtmpfs /dev/shm tmpfs rw,seclabel,relatime 0 0
LINE/dev/mapper/vg_spritty-lv_root / ext4 rw,seclabel,relatime,barrier=1,data=ordered 0 0
LINEnone /selinux selinuxfs rw,relatime 0 0
LINE/proc/bus/usb /proc/bus/usb usbfs rw,relatime 0 0
LINE/dev/sda1 /boot ext4 rw,seclabel,relatime,barrier=1,data=ordered 0 0
FOUND: /boot
paths: ['/dev/vol/backup']
NONE EARLY

(In reply to comment #12)
Okay, maybe I have to add the information that I use two LVM volume groups, one in /dev/sda1 for /dev/vg_spritty/* and the other in /dev/sdb1 for /dev/vol/* . What is interesting is that your function finds the as /boot mounted partition in /dev/sda1 that it is no volume of LVM at all.
Possibly, because there is /dev/sda1 found for modification requested to /dev/vol/backup in /dev/sdb1, this mismatch can not be handled correctly? I guess then system-config-lvm can deal with only one single volume group. But vice versa, trying to modify for example /dev/vg_spritty/home shows similiar results (not mounted ...).
In that case, it would seem to be more like a feature request then. Feel free to close this bug ;)

In any case, it will be possible for me to manage the volumes with the lv* commands in console.

@Raphael:

It usually works correctly with several volume groups. But your output is actually pretty usefull. I know exactly that problem is in function follow_links_to_target(path, paths=[]). As this function is pretty readable then problem can be in
 * you don't have /bin/ls (not usual) :)
 * ls -l /dev/sda -> will not end with date in format '2010-05-05' but it will contains '5 May 2010' (or sth else according to locale). Can you test this second option? There was similar problem before.
You can try also: 
   ls -l --time-style=long-iso /dev/sda

(In reply to comment #14)
[raphael@spritty ~]$ ls -l /dev/sda
brw-rw----. 1 root disk 8, 0  6. Mai 17:12 /dev/sda
[raphael@spritty ~]$ ls -l --time-style=long-iso /dev/sda
brw-rw----. 1 root disk 8, 0 2010-05-06 17:12 /dev/sda

@Raphael:

thanks, I will post patch & create a new build in Friday

Hmm, it will be something slightly different :( 'ls' have to fail 

Can you try:
ls -l /dev/vol/backup; echo $?
ls -l /dev/vg_spritty/lv_root; echo $?

If you use SELinux can you try to turn it off?

It seems to become more like a guessing game. So I am closing the bug with a reference to comment #12 and the hint that it is hardly reproducable.

Raphael please take a look at #597593 -> same problem patch attached

(In reply to comment #19)
Sorry, I have no development system here. Can't test it any more and used the CLI tools.