linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joystick <joystick@shiftmail.org>
To: linux-raid <linux-raid@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Using SCSI timeouts in place of ERC
Date: Mon, 20 Aug 2012 13:37:00 +0200	[thread overview]
Message-ID: <5032215C.9080105@shiftmail.org> (raw)

Hello lists
I am wondering what kind of support I can get from linux for 
"inexpensive" (SATA over SAS HBA in my case) disks on RAID ...
Inexpensive non-raid-edition disks haven't got settable ERC timeout 
(scterc) and can take very long time to respond in case of unreadable sector
However I see an /dev/sdX/device/timeout tunable
Supposing that I accept one disk being dropped from the array at the 
first unreadable sector, can I set that tunable low such as 10sec and 
live happy?

Unfortunately I have read that the expiration of the SCSI timeout can 
trigger a "Host" reset in case the drive does not respond to a reset message
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/task_controlling-scsi-command-timer-onlining-devices.html
would that drop all my drives from the array? That would be a major problem.

Firstly, in "reset the bus": isn't the bus just an electrical wire? How 
can it be "reset" and what does that do? I can understand in the case of 
iSCSI the bus is maybe the TCP socket, I can somehow understand that it 
can be reset, but what about physically attached disks?
I suppose "device" is the disk.. ok for that one, suppose it's doomed
I suppose "host" is the HBA card... so what does a reset of the HBA do? 
Does it drop all the drives and rescan? MD wouldn't react well *at all* 
to this

Thank you
J

                 reply	other threads:[~2012-08-20 11:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5032215C.9080105@shiftmail.org \
    --to=joystick@shiftmail.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-scsi@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).