From: Leonard Lausen <leonard@lausen.nl>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: __btrfs_free_extent error after suspend resume
Date: Fri, 08 Nov 2019 00:08:33 +0000 [thread overview]
Message-ID: <87o8xnw7pa.fsf@lausen.nl> (raw)
In-Reply-To: <7d16efdd-f6f9-9580-d361-a00251b6634c@gmx.com>
Qu Wenruo <quwenruo.btrfs@gmx.com> writes:
>> btrfs check --readonly /dev/$NAME
>>
>> runs out of 16GB of memory within 20 seconds and is killed by the
>> kernel.
>
> That's why we have btrfs check --mode=lowmem
Thank you for pointing this out Qu.
btrfs check --mode=lowmem finds
checksum verify failed on 1383731085312 found 000000CC wanted FFFFFFF5
checksum verify failed on 1383731085312 found 000000CC wanted FFFFFFF5
bad tree block 1383731085312, bytenr mismatch, want=1383731085312, have=15281531241332003907
ERROR: shared extent 1776065458176 referencer lost (parent: 1383731085312)
ERROR: errors found in extent allocation tree or chunk allocation
When creating a backup of the home directory after the filesystem was
mounted ro, only a single log file could not be included in the backup
due to failure to read it.
Is there any way to fix the filesystem, given that btrfs check
--mode=lowmem does not support --repair?
Do you think this corruption is related to some kernel bug, triggered
during suspend / resume cycle? Or could it be simply a harddrive (SSD)
failure? (An extended disk self test did not report any errors though.)
Best regards
Leonard
prev parent reply other threads:[~2019-11-08 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 0:01 __btrfs_free_extent error after suspend resume Leonard Lausen
2019-11-07 2:05 ` Leonard Lausen
2019-11-07 2:30 ` Qu Wenruo
2019-11-08 0:08 ` Leonard Lausen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8xnw7pa.fsf@lausen.nl \
--to=leonard@lausen.nl \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).