All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Dan Christensen <jdc@uwo.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: devices get kicked from RAID about once a month
Date: Thu, 03 Jun 2010 12:37:34 -0400	[thread overview]
Message-ID: <4C07DA4E.70501@tmr.com> (raw)
In-Reply-To: <87sk55mijx.fsf@uwo.ca>

Dan Christensen wrote:
> Bill Davidsen <davidsen@tmr.com> writes:
>
>   
>> Presumably something shows in the logs, that's the next place to look.
>>     
>
> I believe my drives simply don't support adjusting the time it takes to
> try to recover a read (CCTL).  Or did you mean the logs at the time of
> failure?  If so, I posted those in the original message.
>
>   
Those logs don't show any information useful to me which tells me how 
long md waited, and I'm not able to parse any of the res: information to 
gain clarity. It would be nice if someone can parse that, but I can't. 
On timeout an elapsed time output would be nice to indicate what the 
time limit is.

But I do have desktop drives in raid arrays, and they do spin down when 
not in use, and when I access the array after it's been unused I get a 
multi-second delay before my ls info comes back, so clearly there are 
some paths in the SATA handling which don't easily time out.

> Have there been any kernel changes since 2.6.28 that might improve
> reliability of my set-up?  It would be nice if md could be told to try
> again before giving up on the drives.
>
>   
Don't know, Neil might. I sure would like to see a timeout in ms in the 
/sys for the device and a flag for the array to not kick a drive for 
timeout until some number of consecutive timeouts have occurred. Note 
that I'm not suggesting some particular implementation, just some 
tunables. And if only one sector times out, a delayed reconstruct and 
rewrite might fix it. Again, a topic for discussion, not a "do thus" 
suggestion.

I would hope that a drive with multiple partitions would get the 
partitions kicked, not the whole drive at once. So one slow sector 
wouldn't take out multiple arrays.
> Thanks for all of the help so far!
>
> 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
>
>   


-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein


  reply	other threads:[~2010-06-03 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 14:14 devices get kicked from RAID about once a month 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-06-02 18:29 Stefan /*St0fF*/ Hübner
2010-06-03  0:13 ` Neil Brown
2010-06-03 17:00   ` Bill Davidsen

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=4C07DA4E.70501@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jdc@uwo.ca \
    --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 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.