On 05/04/2010 05:28 AM, Vladimir G. Ivanovic wrote:
No help, eh? At the minimum, it would be nice if btrfsck were fixed...
Not sure if the following one will help you to show the metadata, but you
can give it a try and go on using btrfs-debug-tree.
diff --git a/disk-io.c b/disk-io.c
index
on 04/28/2010 01:03 PM Vladimir G. Ivanovic said the following:
I overwrote some part of the first 195641856 bytes of a 1TB (nominal)
btrfs volume (I CTRL-C'd out
before dd finished.) OK, OK, you may stop laughing now. Surely something
similar has happened to
you. No? Then it will,
No help, eh? At the minimum, it would be nice if btrfsck were fixed...
Unfortunately, now btrfs will NOT mount the drive, so I am now
completely without data. The mount error is:
kernel: device fsid c64b56bd1c869bb3-e85f95a29c7dd3ad devid 1
transid 21547 /dev/sdc1
kernel: btrfs bad tree
I overwrote some part of the first 195641856 bytes of a 1TB (nominal)
btrfs volume (I CTRL-C'd out
before dd finished.) OK, OK, you may stop laughing now. Surely something
similar has happened to
you. No? Then it will, someday.
First things first: A huge congratulations to the btrfs team because
