linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David MacKinnon <blaedd@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Recovering from csum errors
Date: Tue, 3 Sep 2013 19:26:10 +1000	[thread overview]
Message-ID: <CAA1QwTbiYGWpxctxOrF67wOzdAr6U6TKR__HZW44c2q9XeVM2w@mail.gmail.com> (raw)
In-Reply-To: <pan$97a5$71cfb7f0$286a61f9$62ed2e15@cox.net>

On 3 September 2013 18:54, Duncan <1i5t5.duncan@cox.net> wrote:
>
> > In case the data is wrong, there may be a reverse CRC32 algorithm
> > implemented. Most likely it's only several bytes which got "flipped".
>
...
>
> But... that flips the entire reason for choosing direct-IO in the first
> place -- performance -- on its head, incurring a **HUGE** slowdown just


Not wanting to put words in the original posters mouth, but I read
that as an offline recovery method (scrub?), rather than real time
recovery attempts. If the frequency of errors is low, then for certain
purposes accepting, a few errors if you had a recovery option might be
acceptable.

As mentioned, nocow is probably best for VM images anyhow, but still :)

-David

  reply	other threads:[~2013-09-03  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 21:41 Recovering from csum errors Rain Maker
2013-09-02 22:00 ` Hugo Mills
2013-09-02 22:28   ` Rain Maker
     [not found]   ` < CAD+_0YqsQRO90Lx1R64h8EE-L=4zrE6CEQGDKy-h=92hLLptWw@mail.gmail.com>
2013-09-03  8:54     ` Duncan
2013-09-03  9:26       ` David MacKinnon [this message]
     [not found]   ` < pan$97a5$71cfb7f0$286a61f9$62ed2e15@cox.net>
     [not found]     ` < CAA1QwTbiYGWpxctxOrF67wOzdAr6U6TKR__HZW44c2q9XeVM2w@mail.gmail.com>
2013-09-03 16:08       ` Duncan

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=CAA1QwTbiYGWpxctxOrF67wOzdAr6U6TKR__HZW44c2q9XeVM2w@mail.gmail.com \
    --to=blaedd@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 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).