From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: gazillions of Incorrect local/global backref count
Date: Sun, 04 Sep 2016 06:50:53 +0200 [thread overview]
Message-ID: <1472964653.8683.17.camel@scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Hey.
I just did a btrfs check on my notebooks root fs, with:
$ uname -a
Linux heisenberg 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28)
x86_64 GNU/Linux
$ btrfs --version
btrfs-progs v4.7.1
during:
checking extents
it found gazillions of these:
Incorrect local backref count on 1107980288 root 257 owner 17807428
offset 13568135168 found 2 wanted 3 back 0x2d69990
Incorrect local backref count on 1107980288 root 257 owner 14055042
offset 13568135168 found 2 wanted 3 back 0x2d69930
Incorrect global backref count on 1107980288 found 4 wanted 6
backpointer mismatch on [1107980288 61440]
Incorrect local backref count on 1108049920 root 257 owner 17807428
offset 13568262144 found 2 wanted 5 back 0x2d69ac0
Incorrect local backref count on 1108049920 root 257 owner 14055042
offset 13568262144 found 2 wanted 5 back 0x2d69b20
Incorrect global backref count on 1108049920 found 4 wanted 10
backpointer mismatch on [1108049920 77824]
See stdout/err[0] logfiles from the check.
What do they mean?
And does this now mean that data is corrupted and I should try to
recover that from a backup?
And if so... how to I map the affected addresses above back to files?
Or can I somehow simply (and foremost cleanly/perfectly) correct these
errors?
Thanks in advance,
Chris.
[0] http://christoph.anton.mitterer.name/tmp/public/dbf3aee0-725a-11e6-8fd0-0019dbacbbbf/
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next reply other threads:[~2016-09-04 4:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 4:50 Christoph Anton Mitterer [this message]
2016-09-04 5:33 ` gazillions of Incorrect local/global backref count Paul Jones
2016-09-04 6:33 ` Christoph Anton Mitterer
2016-09-04 22:41 ` Chris Murphy
2016-09-05 7:27 ` David Sterba
2016-09-05 14:33 ` Christoph Anton Mitterer
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=1472964653.8683.17.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
/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).