From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ata drive capabilities
Date: Wed, 26 Dec 2007 21:34:19 -0500 [thread overview]
Message-ID: <c9ee9d09efb038a1f678a32caabeaecb@quanstro.net> (raw)
In-Reply-To: <20071226195247.GE16180@hermes.my.domain>
> Thanks for your replies!
>
> The reason I asked is that I am thinking about a couple of methods
> to detect failures of my two mirrored disks (by fs) automatically.
> How do you check if your disks are still ok? I know I could invest
> in a real raid controller and rely on that but I still like the
> idea of being independent of yet another piece of hardware which
> internal formatting of the disk is hidden from me..
>
> Kind regards,
>
> Christian
i'm not sure you need that. fs(3) already logs i/o errors which should
be as good an indication of trouble as smart. i/o errors have the benefit
of not being drive dependent. the recovery will need to be done by
hand anway, as fs doesn't have the concept of device state. (there are
some subtile difficulties, too. sometimes drives read an lba correctly
but writes fail.)
for something more automatic, devices would need state and an
online recovery mechanism.
- erik
next prev parent reply other threads:[~2007-12-27 2:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-25 21:40 Christian Kellermann
2007-12-25 21:48 ` Pietro Gagliardi
2007-12-25 23:59 ` erik quanstrom
2007-12-26 6:31 ` ron minnich
2007-12-26 13:10 ` erik quanstrom
2007-12-26 19:52 ` Christian Kellermann
2007-12-26 20:13 ` andrey mirtchovski
2007-12-27 18:12 ` Christian Kellermann
2007-12-26 23:58 ` Robert William Fuller
2007-12-27 2:34 ` erik quanstrom [this message]
2007-12-26 7:44 Joshua Wood
2007-12-26 13:18 ` roger peppe
2007-12-26 18:15 ` erik quanstrom
2007-12-26 16:22 Joshua Wood
2007-12-26 18:14 ` erik quanstrom
2007-12-27 6:22 Joshua Wood
2007-12-27 7:28 ` erik quanstrom
2007-12-27 9:01 Joshua Wood
2007-12-27 15:15 ` Brantley Coile
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=c9ee9d09efb038a1f678a32caabeaecb@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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).