Excerpts from cwillu's message of 2011-05-03 21:50:53 -0400: > On Tue, May 3, 2011 at 7:32 PM, Geoff Ritter <geoff.rit...@gmail.com> wrote: > > Not sure where to report bugs or even find a coherent list of them. Sorry > > if this is already well known. > > > > When attempting to use an unlocked encrypted device as either a seed device > > or the writeable device, a kernel bug will be displayed at > > fs/btrfs/volumes.c:2402 after attempting to add the writeable device to the > > mounted read-only seed. > > > > STR: > > 1. cryptsetup luksFormat /dev/sdx1 > > 2. cryptsetup luksOpen /dev/sdx1 luksSeed > > 3. mkfs.btrfs /dev/mapper/luksSeed > > 4. mount and add files if you want, then unmount > > 5. btrfstune -S 1 /dev/mapper/luksSeed > > 6. mount /dev/mapper/luksSeed /mnt/luksSeed > > 7. btrfs device add /dev/sdx2 /mnt/luksSeed > > 8. Observe kernel BUG. > > > > I would hope to expect to see an error message if this is never intended to > > be possible. But normal btrfs file systems appear to function normally > > under both encrypted and lvm partitions. > > > > This attached kernel message was from two LVM logical volumes on a luks > > encrypted partition. However, I also tested this with two regular > > partitions between endrypted-seed/unencrypted-rw, > > endrypted-rw/unencrypted-seed, and both encrypted.
Ok, looks like I busted the seed support when I fixed up some of the chunk allocations. I'll reproduce this and work out a fix. -chris -- 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
