From: Daniel Pittman <daniel@rimspace.net>
To: linux-raid@vger.kernel.org
Subject: Re: USB disks for RAID storage
Date: Wed, 20 Sep 2006 12:11:56 +1000 [thread overview]
Message-ID: <87irjj4783.fsf@rimspace.net> (raw)
In-Reply-To: b53b67d20609190259v44d7306bya61a487fd055888b@mail.gmail.com
"Patrick Hoover" <phoover.eml@gmail.com> writes:
Top posting makes it hard to keep meaningful context in the discussion.
It would be nice if you would avoid that in future.
[... RAID on USB attached disks ...]
> With USB interfaced disks, it appears that you lose access to the
> SMART capabilities built into the disks. My understanding is that
> there is no way to map the SMART transactions onto USB - it would be
> great if I were mistaken here.
You are mistaken: it is perfectly possible for a USB disk enclosure to
translate SMART requests to the disk.
However you are not very much mistaken: none of them actually /do/ that
translation. So, in practice you do give up on SMART notification of
pending issues.
> There was another thread here on testing arrays a short while ago. My
> take on that was using SMART really was the way to go. However, in
> this case, where SMART doesn't appear to work, what are the best
> options for monitoring disk integrity / degradation?
The case of "where SMART doesn't appear to work" is "if (1)" -- SMART
does not always alert you to a disk failure before it shows up. I say
this from the experience of servers with extensive SMART monitoring that
have failed disks without warning.
So, don't assume that SMART is going to catch every fault for you, or
that you really lose that much without it.[1]
Regards,
Daniel
Footnotes:
[1] I have had one disk failure noted by SMART first, dozens of
failures noted by MD kicking out a disk, and one case where I
swapped out the disk as SMART showed increasing error counts over
the last couple of years.
--
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707 email: contact@digital-infrastructure.com.au
http://digital-infrastructure.com.au/
next prev parent reply other threads:[~2006-09-20 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 12:16 Please help me save my data martin.kihlgren
2006-09-11 13:10 ` Patrick Hoover
2006-09-16 13:14 ` Molle Bestefich
2006-09-16 23:53 ` martin.kihlgren
2006-09-16 23:48 ` USB disks for RAID storage (was Re: Please help me save my data) Daniel Pittman
2006-09-18 8:43 ` Molle Bestefich
2006-09-19 9:59 ` Patrick Hoover
2006-09-20 2:11 ` Daniel Pittman [this message]
2006-09-21 5:25 ` Molle Bestefich
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=87irjj4783.fsf@rimspace.net \
--to=daniel@rimspace.net \
--cc=linux-raid@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 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).