On Thu, 2011-06-02 at 04:20 -0500, C Anthony Risinger wrote: > > i tried with loop devices at first, then "real" devices -- this is all > under KVM/QEMU, and with FSs that are/will be smaller than 1G.
I have tried the seed option as well. I was able to successfully mount the read write partition after setting up the seed. However, both had to be independent partitions on a real device. During testing, both .38 and .39rc could NOT create a seed if one or both partitions were encrypted. I believe encrypted partitions also work with a loop device for the unlocked version you write too. The response I got after a few days is as follows: > Chris Mason chris.ma...@oracle.com > cwillu <cwi...@cwillu.com> > date Thu, May 5, 2011 at 4:42 PM > 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. I just assumed it would take a while to fix so I haven't tried again since. If the root of the problem appears to be loop devices, you might want to report that. Err I guess you did. To me, this doesn't explain why it wouldn't work in a Virtual Machine. I would have thought the VM would treat it as a real device. -- 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
