Output of first btrfs check --repair (also removed all "bad metadata
..." messages). (TL;DR: The repair failed with "Error: could not find
btree root extent for root 1406")
squidock# ./btrfs check --repair /dev/sdc1
enabling repair mode
Checking filesystem on /dev/sdc1
UUID: 14ea871f-1e47-49b3-9f9
> Not attached to this email. :) Can you just put the text inline?
Damn. Here they are.
For the record, I felt dumb since the original files (from a week ago)
were using btrfs-progs 3.19 (I thought I was using 4.2). "Luckily" it
happened again today on another drive, so I'm sending this instead.
On Tue, Sep 22, 2015 at 08:55:05AM -0300, Sylvain Joyeux wrote:
> Hi
>
> Hopefully, third time's the charm ... this time I'm subscribed.
>
> (NB: sorry if you got this twice, but it did not appear in the ML
> archives so I'm assuming it never reached the ML ...)
>
> I am in the situation where a
Hi
Hopefully, third time's the charm ... this time I'm subscribed.
(NB: sorry if you got this twice, but it did not appear in the ML
archives so I'm assuming it never reached the ML ...)
I am in the situation where a partition has errors, detected by
btrfs-check but not repaired by it. Mounting
