To start off, I have an encrypted LVM setup with a root logical volume and a home logical volume. Today decided to upgrade my home LV to btrfs for compression. I installed btrfs-progs, unmounted /home, and ran btrfs-convert /dev/MyVolumeGroup/home and it completed with no errors reported. I rebooted my system, and I got a "Welcome to emergency mode!" message. I rebooted into a live CD and found that all of my logical volumes were showing up, but almost all of them showed status "NOT available". I ran vgck and lvck, both of which found no errors. I ran lvscan and still /dev/MyVolumeGroup/ (and /dev/mapper/MyVolumeGroup-*) contains only one of the LVs.
It seems that btrfs-convert possibly overwrote the LVM metadata somehow, but I have no idea how since the argument was a logical volume. Even if I had accidentally typed /dev/MyVolumeGroup, I would think that btrfs-convert should have realized that it was not an ext2/3/4 filesystem. I tried mounting one of the "available" LVs, and got mount: /dev/MyVolumeGroup/root is write-protected, mounting read only. mount: special device /dev/MyVolumeGroup/root does not exist. I've already started a fresh installation due to time constraints, but I'd like to find out why this happened and let everyone know about a potential bug. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
