All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Mitchell <george@chinilu.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: How does btrfs handle bad blocks in raid1?
Date: Tue, 14 Jan 2014 13:27:30 -0800	[thread overview]
Message-ID: <52D5ABC2.6000505@chinilu.com> (raw)
In-Reply-To: <20140115030021.0b001eeb@natsu>

On 01/14/2014 01:00 PM, Roman Mamedov wrote:
> 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.
Well, sorry, email is nice, but it doesn't work for me as a desktop 
user.  1) I don't want to have to hand configure and email system like 
sendmail to generate outgoing emails.  2) I don't want to have to go 
through and hand configure /etc/smartd/conf.  3) I don't want my email 
clogged up with SMART messages.
>
>> 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
Really?  And for Linux they are?  I know it can be done because various 
administrative tools provided by my distro routinely flash up status 
notices on my screen.  I really like that.  It lets my know what my 
system is doing.  journalctl provides red type warnings when a drive is 
failing.  That should be thrown up on the screen and stay there till I 
dismiss it.  To me thats a no brainer.
>
>> 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.

Well, since I began using SMART I have had a total of two drive failures 
so far and both of them generated warnings and the drives in question 
were still operating normally when I disgarded them. Plenty of 
opportunity to retrieve the data and wipe the drives.  I'm sure SMART 
does fail advance notifictation in some instances, but even when it 
does, at least it will certainly warn me IMMEDIATELY that the drive is 
gone after the fact.
>


  parent reply	other threads:[~2014-01-14 21:28 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
2014-01-14 21:06         ` Hugo Mills
2014-01-14 21:27           ` Chris Murphy
2014-01-14 21:27         ` George Mitchell [this message]
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=52D5ABC2.6000505@chinilu.com \
    --to=george@chinilu.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.