From: "Stefan /*St0fF*/ Hübner" <st0ff@gmx.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: devices get kicked from RAID about once a month
Date: Wed, 02 Jun 2010 20:29:46 +0200 [thread overview]
Message-ID: <4C06A31A.4060907@gmx.net> (raw)
-------- Original-Nachricht --------
Betreff: Re: devices get kicked from RAID about once a month
Datum: Wed, 02 Jun 2010 19:08:58 +0200
Von: Stefan /*St0fF*/ Hübner <st0ff@gmx.net>
Antwort an: st0ff@npl.de
An: Dan Christensen <jdc@uwo.ca>
Am 02.06.2010 18:33, schrieb Dan Christensen:
> John Robinson <john.robinson@anonymous.org.uk> writes:
>
>> My Samsung Spinpoint F1's can have TLER enabled using a more recent
>> smartctl. It's not appeared as part of a formal release yet but a
>> patch went in to r3065 in SVN:
>> http://sourceforge.net/apps/trac/smartmontools/log/trunk/smartmontools
>
> Thanks. I got the svn3077 from Debian testing, but it doesn't seem to
> be supported with my drives:
>
> # smartctl -l scterc /dev/sda
> smartctl 5.40 2010-03-16 r3077 [i686-pc-linux-gnu] (local build)
> Copyright (C) 2002-10 by Bruce Allen,
> http://smartmontools.sourceforge.net
>
> Warning: device does not support SCT Commands
There you have it: the drives are not supporting SCT-ERC. Which I can
say is true: I also own an SP2504C.
>
> Any other suggestions?
Not really, it's up to Neil to export some sysfs-variable, where you
could tune how long a drive may take to respond to some command.
The "trying hard to get the data back" can take up to a few minutes
(somewhere I read about 2, somewhere else about 3 minutes). And what
really is happening is: after some timeout the mdraid "thinks
correctly", that the drive cannot provide the requested sector. To
prevent failure, it reconstructs the "missing" data and issues a write
request. Unfortunately the drive still tries to reconstruct the data
itself and will not respond. After those write requests failing, mdraid
drops the disk.
The ERC-setting is volatile. You'd have to issue it on every reboot,
and on every hotswap. But at first you'd have to get drives that
support this setting.
stefan
>
> Dan
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-06-02 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 18:29 Stefan /*St0fF*/ Hübner [this message]
2010-06-03 0:13 ` devices get kicked from RAID about once a month Neil Brown
2010-06-03 17:00 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2010-06-02 14:14 Dan Christensen
2010-06-02 15:02 ` rsivak
2010-06-02 15:29 ` Dan Christensen
2010-06-02 15:37 ` John Robinson
2010-06-02 16:33 ` Dan Christensen
2010-06-02 17:42 ` Bill Davidsen
2010-06-02 17:49 ` Dan Christensen
2010-06-03 16:37 ` Bill Davidsen
2010-06-03 16:47 ` Dan Christensen
2010-06-03 21:33 ` Neil Brown
2010-06-04 13:30 ` Dan Christensen
2010-06-04 13:50 ` Robin Hill
2010-06-04 15:56 ` Dan Christensen
2010-06-02 19:55 ` Miha Verlic
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=4C06A31A.4060907@gmx.net \
--to=st0ff@gmx.net \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
/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).