From: Hans Kraus <hans@hanswkraus.com>
To: linux-raid@vger.kernel.org
Subject: Timeout question
Date: Mon, 04 Nov 2013 21:07:01 +0100 [thread overview]
Message-ID: <5277FE65.8050001@hanswkraus.com> (raw)
Hi,
I put all my replaced and so on HDs in one machine to serve
backup duties, with backuppc.
I assembled four raid0, each consiting of a 3 + 1 TB couple or
2 + 2 TB couple. Some of these support scterc, some do not. I've
put the following in rc.local (by the way, the system is running
Debian):
cd /dev
for x in sd[a-z]; do
/bin/echo $x
"---------------------------------------------------------------------------"
/usr/sbin/smartctl -s on -o on -S on /dev/$x || echo
"/usr/sbin/smartctl -s on -o on -S on /dev/$x failed."
/usr/sbin/smartctl -l scterc,70,70 /dev/$x || echo 180
>/sys/block/$x/device/timeout || echo "/sys/block/$x/device/timeout not
available"
/usr/sbin/smartctl -t offline /dev/$x || echo "/usr/sbin/smartctl
-t offline /dev/$x failed"
/bin/echo
"-------------------------------------------------------------------------------"
done
Afterwards, these four raid0 are the members of a raid5. The idea
behind this is to be able to replace the raid0 with single 4 TB drives.
Now comes my question: Do I need to care for timeouts of the raid0, and
if so, how do I do that? The following doesn't work:
for x in md??; do
/bin/echo $x
"--------------------------------------------------------------------------"
echo 180 >/sys/block/$x/device/timeout || echo
"/sys/block/$x/device/timeout not available"
/bin/echo
"-------------------------------------------------------------------------------"
done
Kind regards,
Hans
next reply other threads:[~2013-11-04 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 20:07 Hans Kraus [this message]
2013-11-04 22:39 ` Timeout question Phil Turmel
2013-11-04 23:29 ` Keith Keller
2013-11-06 6:49 ` Hans Kraus
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=5277FE65.8050001@hanswkraus.com \
--to=hans@hanswkraus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox