(LVM) Booting fails if a snapshot LV is present on VG

[Matti Lindell]

Edgy Knot2
Kernel : 2.6.17-6-k7

I can reproduce this bug by creating a snapshot of my root filesystem and then reboot using reported kernel. Boot process fails after LV's have been identified on my one and only Volume Group.

[Matti Lindell (mlind)]

When snapshop LV is removed, booting works normally.

[acutler (acutler)]

I can reproduce this too with 2.6.15-26-386 #1 PREEMPT.

Recovery is simple, the device mapped just gets all out of sync. Rejig the devices and remove the snapshot and reboot. eg:

mv /dev/mapper/vg_sys-lv_vmware /dev/mapper/vg_sys-lv_vmware_snap ;
mv /dev/mapper/vg_sys-lv_vmware-real /dev/mapper/vg_sys-lv_vmware;
fsck /dev/mapper/vg_sys-lv_vmware;
lvremove /dev/vg_sys/lv_vmware_snap;
touch /forcefsck;
reboot;

I think its related to my bug https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/71567

[acutler (acutler)]

Clarification, It seems the lv can also be removed without having to hack around with the device mapper.

[reitzmichnicht (reitzmichnicht)]

I had also the problem. One solution is to add

modprobe dm-snapshot >/dev/null 2>&1

to the beginning of /etc/init.d/lvm.

After this the next problem occurs. The device-mapper tries something with the hidden snapshot volumes *-cow and *-real I think:

device-mapper: unknown target type
device-mapper: error adding target to table
device-mapper: unknown target type
device-mapper: error adding target to table

When ignoring the warnings during boot the lvm snapshot works.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Jean-Baptiste Lallement (jibel)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.