[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

Hey guys, I just proceeded from 9.10 to 10.4 LTS lucid, after not upgrading for 2.5 years, I was about to proceed to the latest version. I decided to keep the old grub, for I made a whole-disk-encryprtion and wanted to keep the settings. I dont know if this is the problem with lvm problem adre

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

Documented in the release notes at : In general, filesystems are listed in /etc/fstab by UUID rather than by device name, to ensure that the filesystem can always be found reliab

Re: [Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

On Wednesday 21 April 2010 03:15:32 Steve Langasek wrote: > That doesn't sound weird to me at all, it's exactly what I expected to > hear based on my own testing here. :) No, it's still weird. I can only boot with a mix of UUID and /dev/mapper. For the moment, let's call that reliable. > So if /

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

btw, the udev log you attached shows no record of any of the LVs - which is consistent with them all having been set up during the initramfs, and consistent with them all having group root ownership (it seems). -- When snapshots exists, mountall will not mount the parent partition https://bugs.la

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

That doesn't sound weird to me at all, it's exactly what I expected to hear based on my own testing here. :) So if /dev/mapper devices get mounted correctly in the presence of snapshots, I think we can conclude that there's no bug in lvm2/mountall wrt snapshots. There seems to be a bug preventing

Re: [Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

On Tuesday 20 April 2010 11:07:59 Steve Langasek wrote: > If you convert all your fstab entries to /dev/mapper *except* for the > vg0-opt entry that's currently giving you problems, and you create > snapshots, does the boot work as expected? Weird as it may sound, but it does. Also, the permission

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

It may or may not have been /intentional/, but it's clearly a /bug/ to convert /dev/mapper entries to UUID; and as soon as we can identify the code responsible for such migration (which we haven't yet), that should be fixed. > When I change all LVM entries to /dev/mapper other bugs get in the > wa

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

I was using UUID because Scott James Remnant wrote in bug 563117 that this was intentional. When I change all LVM entries to /dev/mapper other bugs get in the way of testing. I just did that and also removed all snapshots. What happens then is that /opt can't be mounted (/dev/mapper/vg0-opt) # m

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

> Currently using UUID Why are you doing this? As previously stated, it's an error to try to use UUIDs in /etc/fstab for LVs, as UUID is not guaranteed to be unique in the face of snapshotting. The only reason this bug is not cloved as 'invalid' is because you said it occurs even when using LV n

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

** Attachment added: "mountall.log" http://launchpadlibrarian.net/44877195/mountall.log -- When snapshots exists, mountall will not mount the parent partition https://bugs.launchpad.net/bugs/563902 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

I have 2 snapshots of /home (see bug 563117 about this being intentional) Currently using UUID On boot, plymouth says: "Serious errors were found while checking the disk drive for /home" # mount /home mount: /dev/mapper/vg0-home-udsm100420 already mounted or /home busy mount: according to mta

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

I can't reproduce this problem. I've created an lvm snapshot of my /home partition, and /home is still mounted correctly on reboot. When you can get in front of this machine again, please verify whether the expected entries are present under /dev/mapper, and also grab the output of 'lvdisplay'.

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

I don't see any evidence of a mountall bug here - this sounds like an lvm2 issue ** Package changed: mountall (Ubuntu) => lvm2 (Ubuntu) -- When snapshots exists, mountall will not mount the parent partition https://bugs.launchpad.net/bugs/563902 You received this bug notification because you are

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

I can't tell you that. It's possible that /dev/mapper/vg0-home does not exist until after the snapshot is removed. The machine is on another locaten, so I can't see plymouth stuff during reboot) If I remember correctly, ls /dev/mapper does not show vg0-home, but I could be wrong there. >From /etc/

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

Alvin, Sorry, I guess I missed that your example shows 'mount' failing to mount /dev/mapper/vg0-home. When mount gives this error, *does* /dev/mapper/vg0-home exist on the filesystem? What does the fstab entry for this look like? ** Changed in: mountall (Ubuntu) Status: Invalid => New -

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

@Thierry Carrez I'm sorry. I will visit the location of the Lucid machines in 4 days. Due to the nature of the bug, trying this with remote access is impossible for now. @Steve Langasek Maybe I wasn't clear in my description. This will also happen if you use /dev/mapper entries! The bug is in fa

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

If you list your volumes by UUID in /etc/fstab instead of by volume name, mountall has no way to know which one is the right one to mount. LVs should always be listed in /etc/fstab by name which is unique; not by UUID, which may not be. All of the historical scripts in Ubuntu for transitioning /et

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

Might be linked to bug 561390 which shows more random LVM volume mounting failure cases. -- When snapshots exists, mountall will not mount the parent partition https://bugs.launchpad.net/bugs/563902 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 563902] Re: When snapshots exists, mountall will not mount the parent partition

Alvin: could you attach mountall --debug logs ? This works for me: Edit /etc/init/mountall.conf so that the mountall line reads: exec mountall --debug --daemon $force_fsck $fsck_fix > /dev/mountall.log Enter "M" mode: cp /dev/mountall.log /dev/saved.log fix it so that it boots... and attach save