Strangely I repeated the same process on the same system (btrfs-zero-log and mount read-only) and it worked. While it's a concern that repeating the same process gives different results it's nice that I'm getting all my data back. On Sun, 23 Nov 2014, Russell Coker <russell@xxxxxxxxxxxx> wrote: > I have a workstation running Linux 3.14.something on a 120G SSD. It > recently had a problem and now the root filesystem can't be mounted, here > is the message I get when trying to mount it read-only on Debian kernel > 3.16.2-3: > > [4703937.784447] BTRFS info (device loop0): disk space caching is enabled > [4703938.754247] BTRFS: log replay required on RO media > [4703938.794148] BTRFS: open_ctree failed > > When I tried to boot it normally it gave a lot of kernel messages and > failed to mount it. > > Here's the error I get from the btrfs-zero-log in btrfs-tools > 0.19+20130501-1: > > # btrfs-zero-log yayia-corrupt > extent buffer leak: start 157263929344 len 4096 > *** Error in `btrfs-zero-log': corrupted double-linked list: > 0x0000000001068960 *** > Aborted > > I installed btrfs-tools 3.17-1 and then btrfs-zero-log ran without error. > But when I tried to mount the filesystem I got the attached kernel error > when trying to mount with Debian kernel 3.16.2-3. > > Any suggestions on what I should do next? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
