I can confirm that, even with a single-device btrfs filesystem. However
I am curious why you want to use the lvm snapshot capability instead of
the btrfs one.
You can't use btrfs snapshots on a broken FS. LVM snapshots would be
useful to save the original state, before any potentially destructi
On 02/10/2013 01:32 AM, Piotr Pawłow wrote:
> Hello,
>> Yeah you can't mount images, we clear out the chunk tree so
>> nothing works. Let me know if you run into any problems in the
>> future. Thanks,
>
> That's surprising, I haven't seen it mentioned anywhere.
>
> With any other filesystem I co
Hello,
Yeah you can't mount images, we clear out the chunk tree so nothing works.
Let me know if you run into any problems in the future. Thanks,
That's surprising, I haven't seen it mentioned anywhere.
With any other filesystem I could use an LVM snapshot to save the
original state, but wit
On Tue, Feb 05, 2013 at 01:55:17AM -0700, "Piotr Pawłow" wrote:
> > mounts before it panics, can you capture all the output and reply to this
> > email
> > with it? Thanks,
>
> I'm sorry, I could not keep it longer in that state. I used btrfs-image to
> create metadata image from both disks, then
> mounts before it panics, can you capture all the output and reply to this
> email
> with it? Thanks,
I'm sorry, I could not keep it longer in that state. I used btrfs-image to
create metadata image from both disks, then let it run without space
cache.
Unfortunately, when I run qemu with these
On Sun, Feb 03, 2013 at 04:37:58PM -0700, "Piotr Pawłow" wrote:
> Hello,
>
> 1 week ago I bought a new 2TB hard drive, created 1 partition on the whole
> disk, and created root and swap LVM volumes on it. I formatted root to
> btrfs with default options, except meta-data profile which I set to
> "
mount+0x66/0xa0
[] syscall_call+0x7/0xb
---[ end trace 0437071747fbcc24 ]---
[ cut here ]--------
kernel BUG at fs/btrfs/extent-tree.c:1772!
invalid opcode: [#1]
Pid: 309, comm: exe Tainted: GW3.6.0+ #1 Bochs Bochs
EIP: 0060:[] EFLAGS: 00010297 C
