From: George Mitchell <george@chinilu.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: How does btrfs handle bad blocks in raid1?
Date: Thu, 09 Jan 2014 15:24:13 -0800 [thread overview]
Message-ID: <52CF2F9D.4080504@chinilu.com> (raw)
In-Reply-To: <75CB34F7-0BC3-47B7-8817-94F74BC5FD18@colorremedies.com>
I really suspect a lot of bad block issues can be avoided by monitoring
SMART data. SMART is working very well for me with btrfs formatted
drives. SMART will detect when sectors silently fail and as those
failures accumulate, SMART will warn in an obvious way that the drive in
question is at end of life. So I think the whole bad block issue should
ideally be handled at a lower level than filesystem with modern hard drives.
next prev parent reply other threads:[~2014-01-09 23:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 10:26 How does btrfs handle bad blocks in raid1? Clemens Eisserer
2014-01-09 10:42 ` Hugo Mills
2014-01-09 12:41 ` Duncan
2014-01-09 12:52 ` Austin S Hemmelgarn
2014-01-09 15:15 ` Duncan
2014-01-09 16:49 ` George Eleftheriou
2014-01-09 17:09 ` Hugo Mills
2014-01-09 17:34 ` George Eleftheriou
2014-01-09 17:43 ` Hugo Mills
2014-01-09 18:40 ` George Eleftheriou
2014-01-09 17:29 ` Chris Murphy
2014-01-09 18:00 ` George Eleftheriou
2014-01-10 15:27 ` Duncan
2014-01-10 15:46 ` George Mitchell
2014-01-09 17:31 ` Chris Murphy
2014-01-09 18:20 ` Austin S Hemmelgarn
2014-01-09 14:58 ` Chris Mason
2014-01-09 18:08 ` Chris Murphy
2014-01-09 18:22 ` Austin S Hemmelgarn
2014-01-09 18:52 ` Chris Murphy
2014-01-10 17:03 ` Duncan
2014-01-09 18:40 ` Chris Murphy
2014-01-09 19:13 ` Kyle Gates
2014-01-09 19:31 ` Chris Murphy
2014-01-09 23:24 ` George Mitchell [this message]
2014-01-10 0:08 ` Clemens Eisserer
2014-01-10 0:46 ` George Mitchell
[not found] <201401100106.s0A16CNd016476@atl4mhib27.myregisteredsite.com>
2014-01-10 1:31 ` George Mitchell
2014-01-14 19:13 ` Chris Murphy
2014-01-14 19:37 ` Roman Mamedov
2014-01-14 21:05 ` Chris Murphy
2014-01-14 21:19 ` Roman Mamedov
2014-01-14 21:37 ` Chris Murphy
2014-01-14 21:45 ` Chris Murphy
2014-01-14 21:54 ` Roman Mamedov
2014-01-14 20:29 ` George Mitchell
2014-01-14 21:00 ` Roman Mamedov
2014-01-14 21:06 ` Hugo Mills
2014-01-14 21:27 ` Chris Murphy
2014-01-14 21:27 ` George Mitchell
2014-01-14 21:28 ` George Mitchell
2014-01-14 21:14 ` Chris Murphy
2014-01-14 21:48 ` George Mitchell
2014-01-14 21:48 ` George Mitchell
2014-01-14 22:14 ` George Mitchell
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=52CF2F9D.4080504@chinilu.com \
--to=george@chinilu.com \
--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 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.