From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Ravi Hale <tom@hale.ee>, linux-btrfs@vger.kernel.org
Subject: Re: How to repair errors only found with check --mode=lowmem
Date: Mon, 18 Dec 2017 15:17:58 +0800 [thread overview]
Message-ID: <245e7c42-2ea6-7f03-c5d2-52a326a4ed7c@gmx.com> (raw)
In-Reply-To: <16068704b70.277a.1243720eb903aaa2f74f5d2a8df9f525@hale.ee>
[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]
On 2017年12月18日 15:04, Ravi Hale wrote:
> My bad. 4.14.
Well, things get interesting now.
Although there are several new lowmem fixes pending for v4.14.1, the
backref mismatch bug should be addressed in v4.14.
Anyway, would you please try this branch to see if it solves the false
alerts?
https://github.com/kdave/btrfs-progs/commits/devel
If the devel branch still reports error, we still have good enough
sample to dig further.
>> ERROR: extent[691815358464, 11042816] referencer count mismatch
(root: 257, owner: 1869679, offset: 613974016) wanted: 1, have: 2
This is a pretty good sample, small enough to find out what's going on.
Ff devel branch can't help you, would you please dump the output of the
following commands?
# btrfs-debug-tree -t extent /dev/mapper/vg_svelte-home |\
grep -C10 691815358464
# btrfs-debug-tree -t 257 /dev/mapper/vg_svelte-home |\
grep -C20 1869679
Please note that, the 2nd output may contain *FILENAMES*, so feel free
to erase any file name if it's sensitive.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
prev parent reply other threads:[~2017-12-18 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 15:41 How to repair errors only found with check --mode=lowmem Tom Hale
2017-12-18 1:10 ` Qu Wenruo
2017-12-18 7:04 ` Ravi Hale
2017-12-18 7:17 ` Qu Wenruo [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=245e7c42-2ea6-7f03-c5d2-52a326a4ed7c@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tom@hale.ee \
/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