From: Graham Cobb <g.btrfs@cobb.uk.net>
To: Christopher Staples <mastercatz@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: bad sector / bad block support
Date: Wed, 27 Nov 2019 15:42:38 +0000 [thread overview]
Message-ID: <dab2a48c-6cdd-984e-50b8-c75b5f1f9455@cobb.uk.net> (raw)
In-Reply-To: <c1473267-688c-201f-11e5-64761ad51f79@gmail.com>
On 27/11/2019 14:15, Austin S. Hemmelgarn wrote:
> On 2019-11-26 22:30, Christopher Staples wrote:
>> will their ever be a better way to handle bad sectors ? I keep
>> getting silent corruption from random bad sectors
>> scrubs keep passing with out showing any errors , but if I do a
>> ddrescue backup to a new drive I find the bad sectors
> Zygo is correct, if there are no checksum errors, it's almost certainly
> not the storage device.
>
> Put simply, for a media error to cause corruption without a checksum
> error, all of the following need to happen at the same time:
Or, of course, be using NOCOW (or other no-checksum) files.
next prev parent reply other threads:[~2019-11-27 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 3:30 bad sector / bad block support Christopher Staples
2019-11-27 3:48 ` Zygo Blaxell
2019-11-27 14:15 ` Austin S. Hemmelgarn
2019-11-27 15:42 ` Graham Cobb [this message]
2019-11-28 1:23 ` Chris Murphy
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=dab2a48c-6cdd-984e-50b8-c75b5f1f9455@cobb.uk.net \
--to=g.btrfs@cobb.uk.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mastercatz@gmail.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).