From: Roman Mamedov <rm@romanrm.net>
To: george@chinilu.com
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: How does btrfs handle bad blocks in raid1?
Date: Wed, 15 Jan 2014 03:00:21 +0600 [thread overview]
Message-ID: <20140115030021.0b001eeb@natsu> (raw)
In-Reply-To: <52D59E28.7010200@chinilu.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Tue, 14 Jan 2014 12:29:28 -0800
George Mitchell <george@chinilu.com> wrote:
> what we are lacking at this point is a SMART capability to provide
> visual notifications to the user when any hard drive starts to seriously
> degrade or suddenly fails.
You can configure smartd (from smartmontools) to send you E-Mails on any
change of the monitored SMART attributes.
> If SMART were capable of launching pop up warnings
And I'm sure there are a number of GUI tools out there for just about any OS,
which can do just that
> btrfs would not have to worry so much about arrays going simplex undetected.
That said, do not fall into a false sense of security relying on proprietary,
barely if ever updated after the device has been shipped, and often very
peculiar-behaving SMART routines inside the black-box HDD firmware as your
most important data safeguard.
Of course SMART must be checked and monitored, but don't delude yourself into
thinking it will always warn you of anything going wrong well in advance of
failure, or even at all.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-14 21:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201401100106.s0A16CNd016476@atl4mhib27.myregisteredsite.com>
2014-01-10 1:31 ` How does btrfs handle bad blocks in raid1? 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 [this message]
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
2014-01-09 10:26 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
2014-01-10 0:08 ` Clemens Eisserer
2014-01-10 0:46 ` 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=20140115030021.0b001eeb@natsu \
--to=rm@romanrm.net \
--cc=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.