All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: linux-btrfs@vger.kernel.org
Subject: [[PATCH] 0/3] btrfs-check: Fix bitflipped keys from bad RAM
Date: Mon,  5 May 2014 18:07:48 +0100	[thread overview]
Message-ID: <1399309671-9240-1-git-send-email-hugo@carfax.org.uk> (raw)

If you have RAM with stuck or unreliable bits in it, and a metadata block is
stored in it, you can end up with keys with errors in. These usually show up
as "bad key order". In many cases, these out-of-order keys can be identified
and fixed with a simple heuristic. This patch series implements that
heuristic, and fixes a long-standing issue with the existing code to fix out-
of-order keys.

Hugo Mills (3):
  btrfs check: Fix wrong level access
  btrfs check: Pre-sort keys in a block while searching
  btrfs check: Attempt to fix misordered keys with bitflips in them

 cmds-check.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-----
 ctree.c      |  86 ++++++++++++++++++++++++++++++++++++--------
 ctree.h      |   2 ++
 3 files changed, 180 insertions(+), 22 deletions(-)

-- 
1.9.2


             reply	other threads:[~2014-05-05 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 17:07 Hugo Mills [this message]
2014-05-05 17:07 ` [PATCH 1/3] btrfs check: Fix wrong level access Hugo Mills
2014-05-05 17:07 ` [PATCH 2/3] btrfs check: Pre-sort keys in a block while searching Hugo Mills
2014-05-05 17:07 ` [PATCH 3/3] btrfs check: Attempt to fix misordered keys with bitflips in them Hugo Mills
2014-05-16 14:22   ` David Sterba
2014-05-16 14:43     ` Hugo Mills

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=1399309671-9240-1-git-send-email-hugo@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --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.