linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@suse.de>
Cc: st0ff@npl.de, st0ff@gmx.net, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: devices get kicked from RAID about once a month
Date: Thu, 03 Jun 2010 13:00:33 -0400	[thread overview]
Message-ID: <4C07DFB1.4060006@tmr.com> (raw)
In-Reply-To: <20100603101359.01f61d0d@notabene.brown>

Neil Brown wrote:
> On Wed, 02 Jun 2010 20:29:46 +0200
> Stefan /*St0fF*/ Hübner <st0ff@gmx.net> wrote:
>
>   
>>> 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.
>>
>>     
>
> Nope.  md doesn't do any timeouts.
>   

That's the problem. A timeout between getting the timeout status and 
trying the rewrite is really needed to have any hope of recovery.

If there were a write intent bitmap for the drive, perhaps the drive 
could enter some "may be recovering" state and writes, including the one 
to rewrite the sector, could be help off for some few minutes. I say 
that, knowing that there is at least some similar code working for 
network attached drives, which seem to survive a brief network issue.

Telling the user a write intent bitmap is needed and making use of it 
sound at all practical as a use for some existing code?

> You need to look for, or ask for, such variables at the scsi/sata layer.
>
>   
The need for a delay between timeout and rewrite

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


--
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

  reply	other threads:[~2010-06-03 17:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 18:29 devices get kicked from RAID about once a month Stefan /*St0fF*/ Hübner
2010-06-03  0:13 ` Neil Brown
2010-06-03 17:00   ` Bill Davidsen [this message]
  -- 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=4C07DFB1.4060006@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=st0ff@gmx.net \
    --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).