From: Phil Turmel <philip@turmel.org>
To: Chris <email.bug@arcor.de>, linux-raid@vger.kernel.org
Subject: Re: What are mdadm maintainers to do?
Date: Mon, 16 Feb 2015 14:44:11 -0500 [thread overview]
Message-ID: <54E2488B.5060903@turmel.org> (raw)
In-Reply-To: <loom.20150216T183419-387@post.gmane.org>
On 02/16/2015 12:48 PM, Chris wrote:
>
> Thank you for the additional information, it calls for action.
>
>
> OK, calling for a solution to stop desktop drives from causing data loss and
> affecting the mdadm reputation:
>
>
> I gather that mdadm could ship with one additional udev rule that calls a
> script to check/set scterc, or falls back to increasing the system timout.
>
> Phil, you mentioned having posted such a script, could you prepare it for
> addition to the mdadm package?
No, I've posted snippets for users to customize in their own rc.local or
distro equivalent. I vaguely recall posting a generic script for some
common cases, but I've personally converted to raid-rated drives
everywhere in the past couple years.
Somebody else will have to tackle this.
> Would maintainers be ok with adding such a udev rule and script to the package?
Not my call, but keep in mind that this will add a dependency on
smartmontools or whatever means is used to access/write to scterc.
Phil
next prev parent reply other threads:[~2015-02-16 19:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 21:59 re-add POLICY Chris
2015-02-15 19:03 ` re-add POLICY: conflict detection? Chris
2015-02-16 3:28 ` re-add POLICY NeilBrown
2015-02-16 12:23 ` Chris
2015-02-16 13:17 ` Phil Turmel
2015-02-16 16:15 ` desktop disk's error recovery timouts (was: re-add POLICY) Chris
2015-02-16 17:19 ` desktop disk's error recovery timouts Phil Turmel
2015-02-16 17:48 ` What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts) Chris
2015-02-16 19:44 ` Phil Turmel [this message]
2015-02-16 23:49 ` NeilBrown
2015-02-17 7:52 ` What are mdadm maintainers to do? (error recovery redundancy/data loss) Chris
2015-02-17 8:48 ` Mikael Abrahamsson
2015-02-17 10:37 ` Chris
2015-02-17 19:33 ` Chris Murphy
2015-02-17 22:47 ` Adam Goryachev
2015-02-18 1:02 ` Chris Murphy
2015-02-18 11:04 ` Chris
2015-02-19 6:12 ` Chris Murphy
2015-02-20 5:12 ` Roger Heflin
2015-02-17 23:33 ` Chris
2015-02-18 15:04 ` help with the little script (erc timout fix) Chris
2015-02-18 21:25 ` NeilBrown
2015-02-17 15:09 ` re-add POLICY Chris
2015-02-22 13:23 ` Chris
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=54E2488B.5060903@turmel.org \
--to=philip@turmel.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.