linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Read i/o errs and disk replacement
Date: Tue, 18 Feb 2014 22:45:11 +0000 (UTC)	[thread overview]
Message-ID: <pan$c1dcd$ac5efec2$1a07a461$61630cbf@cox.net> (raw)
In-Reply-To: 6B9DC823-92CF-4ECC-979F-C512072DF883@colorremedies.com

Chris Murphy posted on Tue, 18 Feb 2014 15:02:51 -0700 as excerpted:

>  Also, what model drives are being used? If they are
> consumer drives, they almost certainly have long error recoveries over
> 30 minutes.

FWIW, that should be 30 seconds, not 30 minutes (OUCH!).  The below 
context sort of makes that clear for those good enough at reading between 
the lines, thus the suggestion to change the kernel timeout to 121 
seconds, but just in case...

> And if the drive is trying to honor the read request for
> more than 30 seconds, the default SCSI block layer will time out and
> produce messages like what we see here. So you probably need to change
> the SCSI block layer timeout. To set the command timer to something else
> use:
> 
> echo <value> /sys/block/<device>/device/timeout
> 
> Where value is e.g. 121 since many consumer drives time out at 120
> seconds this means the kernel will wait 121 seconds before starting its
> error handling (which includes resetting the drive and then the bus).

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-02-18 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 13:19 Read i/o errs and disk replacement Wolfgang Mader
2014-02-18 18:48 ` Chris Murphy
2014-02-18 21:33   ` Wolfgang Mader
2014-02-18 22:02     ` Chris Murphy
2014-02-18 22:45       ` Duncan [this message]
2014-02-18 23:12         ` Chris Murphy
2014-02-19 20:05       ` Wolfgang Mader
2014-02-18 22:54   ` Duncan

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='pan$c1dcd$ac5efec2$1a07a461$61630cbf@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@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).