From: Chris <email.bug@arcor.de>
To: linux-raid@vger.kernel.org
Subject: smartctl-timeouts_v1.0 (erc timeout fix)
Date: Fri, 27 Feb 2015 13:31:35 +0100 [thread overview]
Message-ID: <20150227133135.673e2261@smtp.arcor.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
Hi,
here they are now. The smartctl-timeouts scripts fix commonly
mismatching defaults with drives that have no error recovery timeout
configured, which has often lead to data loss.
To test, extract the files to /etc/udev/rules.d/ and
*reboot*. For me, the rules somehow had no effect without
rebooting.
Please test, report, and then ship it with smartctl/mdadm.
Cheers,
Chris
[-- Attachment #2: smartctl-timeouts_v1.0.zip --]
[-- Type: application/zip, Size: 10355 bytes --]
reply other threads:[~2015-02-27 12:31 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=20150227133135.673e2261@smtp.arcor.de \
--to=email.bug@arcor.de \
--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;
as well as URLs for NNTP newsgroup(s).