All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Freitas <sflist@ihonk.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs volume mounts and dies (was Re: Segfault in btrfsck)
Date: Wed, 06 Jan 2010 07:59:55 -0800	[thread overview]
Message-ID: <1262793595.6214.5.camel@phat> (raw)
In-Reply-To: <20100106075253.GA5665@cumulus>

Hi Sander,

On Wed, 2010-01-06 at 08:52 +0100, Sander wrote:
> I don't have your original mail, but I think I remember you mentioned a
> lot of bad sectors on that disk reported by SMART.
> 
> If that is indeed the case it might be dificult for the people who might
> be able to help you, to help you.

Thanks for your  response. You're correct about the bad sector warning.
So please correct me if I have some mistaken assumptions. I thought
btrfs would be tolerant of that -- if a block failed the checksum test,
it would reconstruct and remap it. (Also, I assumed that if a drive
hadn't filled its bad sector remapping table, it could handle it at the
hardware level, and SMART's warning was just that -- a warning, not a
dire pronouncement of utter unsuitability -- but that's something else.)

Steve


  reply	other threads:[~2010-01-06 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 23:56 Segfault in btrfsck Steve Freitas
2010-01-03 22:57 ` btrfs volume mounts and dies (was Re: Segfault in btrfsck) Steve Freitas
2010-01-04  0:37   ` Steve Freitas
2010-01-05 22:55     ` Steve Freitas
2010-01-06  7:52       ` Sander
2010-01-06 15:59         ` Steve Freitas [this message]
2010-01-06 17:24           ` Johannes Hirte
2010-01-06 20:11             ` Steve Freitas
2010-01-07  8:23               ` Sander
2010-01-07 18:28             ` What protection does btrfs checksumming currently give? (Was Re: btrfs volume mounts and dies (was Re: Segfault in btrfsck)) Steve Freitas
2010-01-07 19:29               ` jim owens
2010-01-07 21:00                 ` Johannes Hirte

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=1262793595.6214.5.camel@phat \
    --to=sflist@ihonk.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.