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 12:11:35 -0800 [thread overview]
Message-ID: <1262808695.6214.9.camel@phat> (raw)
In-Reply-To: <201001061824.37159.johannes.hirte@fem.tu-ilmenau.de>
Hi Johannes,
On Wed, 2010-01-06 at 18:24 +0100, Johannes Hirte wrote:
> Am Mittwoch 06 Januar 2010 16:59:55 schrieb Steve Freitas:
> > 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.
> Only if enough redundancy is left. And with the default setup btrfs is only
> mirroring the metadata not the data.
Okay. What capacity does btrfs have for reconstructing data, and how do
I enable it (if any) for a new partition? I think I've confused
checksums with magical ponies.
> Bad sectors are only remapped by the drive on write time. As long as this
> isn't the case, they are only marked as pending. As you have written, that
> SMART detected many bad blocks, I suspect the FS is really damaged. And as
> btrfsck is limited, I don't think it can fix this.
Alright, I'll trash it and start over with a different drive.
Thanks,
Steve
next prev parent reply other threads:[~2010-01-06 20:11 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
2010-01-06 17:24 ` Johannes Hirte
2010-01-06 20:11 ` Steve Freitas [this message]
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=1262808695.6214.9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox