From: <hoegge@gmail.com>
To: <linux-btrfs@vger.kernel.org>
Subject: BTRFS checksum mismatch - false positives
Date: Mon, 23 Sep 2019 20:19:24 +0200 [thread overview]
Message-ID: <000f01d5723b$6e3d0f70$4ab72e50$@gmail.com> (raw)
Dear BTRFS mailing list,
I'm running BTRFS on my Synology Diskstation and they have referred me to
the BTRFS developers.
For a while I have had quite a few (tens - not hundreds) checksum mismatch
errors on my device (around 6 TB data). It runs BTRFS on SHR (Synology
Hybrid Raid). Most of these checksum mismatches, though, do not seem "real".
Most of the files are identical to the original files (checked by binary
comparison and by recalculated MD5 hashes).
What can explain that problem? I thought BTRFS only reported checksum
mismatch errors, when it cannot self-heal the files?
Best
Hoegge
next reply other threads:[~2019-09-23 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 18:19 hoegge [this message]
2019-09-23 19:11 ` BTRFS checksum mismatch - false positives Chris Murphy
2019-09-23 20:24 ` hoegge
2019-09-23 20:59 ` Chris Murphy
2019-09-24 9:29 ` hoegge
2019-09-24 21:46 ` Chris Murphy
2019-09-24 13:42 ` hoegge
2019-09-24 22:05 ` Chris Murphy
2019-09-26 20:27 ` Chris Murphy
2019-09-30 9:31 ` hoegge
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='000f01d5723b$6e3d0f70$4ab72e50$@gmail.com' \
--to=hoegge@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.