I've found a workaround: - recover the filesystem image (either by doing math with lvdisplay -m/pvdisplay -m, correlating with dmsetup table output for other volumes, or by trying to activate the LV and looking at dmsetup table for the subvolumes directly)
- possibly reboot if you tried to activate and now the kernel lock is wedged - remove the broken logical volume with lvremove - re-create a new volume of the same size, dd the recovered image onto it I still have dumps of the metadata subvolumes (jenkins_rmeta_0 and jenkins_rmeta_1, they differ by exactly one bit at offset 13 decimal) if those could be useful for debugging the kernel's md_bitmap_read_sb code. They're 4 MB each and I'm not sure I can attach them to this Launchpad bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103596 Title: Activating a LVM RAID-1 volume causes a kernel BUG: "detected buffer overflow in strlen" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
