From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Christopher Staples <mastercatz@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: bad sector / bad block support
Date: Tue, 26 Nov 2019 22:48:39 -0500 [thread overview]
Message-ID: <20191127034838.GL22121@hungrycats.org> (raw)
In-Reply-To: <CAGsZeXsEZ8EqPsuU9O+7d+suxBVNQAobASJaLNMZB9LhUe6Q7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Wed, Nov 27, 2019 at 01:30:04PM +1000, 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
That is a typical symptom of host RAM corruption. Make sure your memory
and CPU are OK.
A similar test you can do is to copy a large file or group of files
(say a few GB) and compare the copy with the original. If there are
differences but no btrfs csum errors, chances are good that you are
looking at some kind of host RAM failure.
> the only thing I can do for now is mark I/O error files as bad buy
> renaming them and make another file copy onto the file system ,
>
>
> I like btrfs for the snapshot ability , but when it comes to keeping
> data safe ext4 seems better ? at least it looks for bad sectors and
> marks them , btrfs just seems to write and assumes its written ..
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-11-27 3:48 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 [this message]
2019-11-27 14:15 ` Austin S. Hemmelgarn
2019-11-27 15:42 ` Graham Cobb
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=20191127034838.GL22121@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--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