From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: ignoring bad blocks
Date: Sun, 4 Jan 2015 07:18:43 -0800 [thread overview]
Message-ID: <20150104151843.GX17254@merlins.org> (raw)
In-Reply-To: <CAJCQCtRYW_S8CDZQH_95RGtsTBHN3gftd9WgsScA7_oCpFYgOg@mail.gmail.com>
On Sun, Jan 04, 2015 at 01:45:41AM -0700, Chris Murphy wrote:
> On Sat, Jan 3, 2015 at 10:40 PM, Dyweni - BTRFS <Y4BwxfPC4k5h@dyweni.com> wrote:
> > Hi All,
> >
> > Can BTRFS ignore bad blocks as they are discovered?
> >
> > I want to try BTRFS on some older drives, but they all have a few bad
> > blocks.
>
> Not currently, and I don't see it in the project ideas list. Right now
> on Btrfs you will just get write errors, but I'm uncertain if it just
> tries a new sector and continues on (indirectly not use the bad sector
> but also not keeping track of it either)? The unreliable disk features
> are still project ideas.
badblocks are a thing of the past, as you hinted drives automatically
remap badblocks so that the filesystem doesn't have to deal with them.
If you have a questionable drive, you can indeed simply dd 0's over it
before you use it with btrfs.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2015-01-04 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 5:40 ignoring bad blocks Dyweni - BTRFS
2015-01-04 8:45 ` Chris Murphy
2015-01-04 15:18 ` Marc MERLIN [this message]
2015-01-04 20:46 ` Chris Murphy
2015-01-10 1:44 ` Russell Coker
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=20150104151843.GX17254@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).