| Summary: | diskdrake fails to recognize LVM group contents | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Simple <simplew8> |
| Component: | RPM Packages | Assignee: | Pascal Terjan <pterjan> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Simple
2012-05-07 12:06:08 CEST
Thierry Vignaud
2012-05-07 18:54:20 CEST
CC:
(none) =>
thierry.vignaud I don't understand. Where are you running diskdrake from? From the running system? Yes, from the kde session as root runned diskdrake and in the LVM volume i see that the partitions dont appear with the mount points set. Partitions root and home appears without mount points set, also the swap partition now appears in the right, when i did put it in the middle of the /partition and /home partition. Hmm there is something really wrong, you shouldn't need to enter the password, the encrypted volume is already available if the partitions are currently mounted. Sorry, i missconfused that part, you dont need to enter anby passphrase for the LVM volume where the system partitions are, the problem is about not showing the partitions in correct order and show the partitions without any mount point set. There's no correct order for LVs. Depending on resizing history, the physical extents they use can be intermixed... Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO This continues being a valid bug in Mageia 2 and cauldron
Simple
2012-05-27 04:15:05 CEST
Keywords:
NEEDINFO =>
(none) Thierry for what i see, diskdrake regarding LVM volumes, does not recognize whats in /etc/fstab. When running drakdisk and i click in LVM volume group root and home, it doesnt show its mount point and neither its options (acl and noatime dont appear selected) and in /etc/fstab it haves this: /dev/mapper/insys-root / ext4 acl,noatime 1 1 /dev/mapper/insys-home /home ext4 acl,noatime 1 2 I can confirm that without encryption, diskdrake shows the mountpoint for a partition that is not in a lvm volume group, but doesn't show the mountpoint for one that is in a lvm volume group, where both partitions are mounted. CC:
(none) =>
davidwhodgins It works fine here, but fstab contains entries like: /dev/big/chroots /mnt/chroots ext3 relatime 1 2 Not /dev/mapper/* Its correct, if in fstab it haves: /dev/`LVM Group name`/`logical volume name` than diskdrake correctly shows the mount point and options. Diskdrake also show correctly if using UUID in fstab: UUID=4d6959ef-6116-4810-b277-d6cdfbabbba1 / ext4 acl,noatime 1 1 so why diskdrake doesnt shows when using /dev/mapper ? Now, this is weird, i have changed home and root logical volumes in fstab to: /dev/`LVM Group name`/`logical volume name` so fstab was like this: /dev/insys/root / ext4 acl,relatime 1 1 /dev/insys/home /home ext4 acl,noatime 1 2 I run drakdisk and changed an option in another partition (not LVM), in which drakdisk asks if the changes should be saved in /etc/fstab, i answer yes. I go back to /etc/fstab and see that ALL LVM entries were changed (and the option i changed wasnt even in a LVM volume), see hows fstab is now: /dev/mapper/insys-root / ext4 acl,relatime 1 1 /dev/mapper/insys-home /home ext4 acl,noatime 1 2 So drakdisk changes the LVM entries in fstab to start with "/dev/mapper/" and then when running again drakdisk it does NOT recognize them. In this bug report we 2 problems: 1- drakdisk does not recognize /dev/mapper 2- changes LVM entries to start with /dev/mapper in fstab everytime a change is performed in ANY partition Im closing this bug report since the first report was about diskdrake not being able to recognize lv's mount points, but i have figured out why that was happening, and was due to cypher changes. Status:
NEW =>
RESOLVED |