On 2016-09-13 16:39, Cesar Strauss wrote:
On 13-09-2016 16:49, Austin S. Hemmelgarn wrote:
I'd be kind of curious to see the results from btrfs check run without
repair, but I doubt that will help narrow things down any further.
Attached.
As of right now, the absolute first thing I'd do is
>From the fsck...
bad block 160420741120
I can't tell though if that's a bad Btrfs leaf/node where both dup
copies are bad; or if it's a bad sector.
I'd mount it ro, and take a backup of anything you care about before
proceeding further.
smartctl -x might reveal if there are problems the drive
On 13-09-2016 16:39, Chris Murphy wrote:
I just wouldn't use btrfs repair with this version of progs, go back
to v4.6.1 or upgrade to 4.7.2.
Thanks for the tip. I upgraded to 4.7.2.
Cesar
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to maj
On 13-09-2016 16:49, Austin S. Hemmelgarn wrote:
I'd be kind of curious to see the results from btrfs check run without
repair, but I doubt that will help narrow things down any further.
Attached.
As of right now, the absolute first thing I'd do is check your logs to
see if you can find any
On Tue, Sep 13, 2016 at 1:49 PM, Austin S. Hemmelgarn
wrote:
> On 2016-09-13 15:20, Cesar Strauss wrote:
>>
>> btrfs-progs v4.7
>
> It's always good to see people who are staying up-to-date on the kernel and
> userspace :)
Yes, although it and 4.7.1 are marked as do not use.
https://btrfs.wiki.
On 2016-09-13 15:20, Cesar Strauss wrote:
Hello,
I have a BTRFS filesystem that is reverting to read-only after a few
moments of use. There is a stack trace visible in the kernel log, which
is attached.
Here is my system information:
# uname -a
Linux rescue 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug
I just wouldn't use btrfs repair with this version of progs, go back
to v4.6.1 or upgrade to 4.7.2. You could do an offline check (no
repair) and see if that reveals anything useful for developers. But I
can't tell what's going on from the call trace.
--
Chris Murphy
--
To unsubscribe from thi
Hello,
I have a BTRFS filesystem that is reverting to read-only after a few
moments of use. There is a stack trace visible in the kernel log, which
is attached.
Here is my system information:
# uname -a
Linux rescue 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016
x86_64 GNU/Linux