linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris <email.bug@arcor.de>
To: smartmontools-support@lists.sourceforge.net, linux-raid@vger.kernel.org
Subject: smartctl-timeouts_v1.01 scripts (scterc timeout fixes)
Date: Thu, 5 Mar 2015 19:21:34 +0100	[thread overview]
Message-ID: <20150305192134.3a6c0b8e@smtp.arcor.de> (raw)
In-Reply-To: <20150227144951.648ba949@smtp.arcor.de>

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]


Hello list,

could readers please respond with a short yes/no, if they would like
smartctl scripts that fix mismatching scterc/controller timeouts to
prevent data loss?
(Testing them only requires to unzip the file into /etc/udev/rules.d/)


And dear maintainers, would you consider shipping the
scripts?
(Fixing the timeouts seems important for all systems without a
default  smartctl -l scterc timeout. And all redundancy controlling
packages (mdadm, lvm, btrfs, ...) may want to suggest or depend on the
smartctl package and set shorter timeouts, i.e. they call the
appropriate scripts depending on redundancy states. Thus smartctl seems
the right package to ship the scripts and default udev rule, and other
packages ship their device specific udev rules.)

Cheers,
Chris


PS: v1.01 has smartctl-default_test.rules for udev and is working well
here with drives that have scterc timeout default to "Disabled".



Am Fri, 27 Feb 2015 14:49:51 +0100
schrieb Chris <email.bug@arcor.de>:

> 
> Hi there,
> 
> here are some "smartctl-timeouts" scripts that fix commonly
> mismatching defaults with drives that have no error recovery timeout
> configured, which has often lead to data loss. (See the README for
> further information.)
> 
> The scripts are the result of discussions on the linux-raid
> mailinglist, but it may be best to ship the scripts with smartctl
> already (possibly together with a default "non-redundant-disk" udev
> rule to ensure proper default timeouts), and let redundancy
> controlling packages like mdadm, lvm, btrfs etc. ship their own udev
> rules to call the scripts appropriately.
> 
> Please respond whether you'd like to ship the scripts together with
> smartctl.
> 
> Cheers,
> Chris



[-- Attachment #2: smartctl-timeouts_v1.01.zip --]
[-- Type: application/zip, Size: 11266 bytes --]

           reply	other threads:[~2015-03-05 18:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20150227144951.648ba949@smtp.arcor.de>]

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=20150305192134.3a6c0b8e@smtp.arcor.de \
    --to=email.bug@arcor.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    /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).