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
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 ; vg_sys- lv_vmware- real /dev/mapper/ vg_sys- lv_vmware; vg_sys- lv_vmware; sys/lv_ vmware_ snap;
mv /dev/mapper/
fsck /dev/mapper/
lvremove /dev/vg_
touch /forcefsck;
reboot;
I think its related to my bug https:/ /launchpad. net/distros/ ubuntu/ +source/ linux-source- 2.6.17/ +bug/71567