From: NeilBrown <neilb@suse.de>
To: dag@newtech.fi
Cc: linux-raid@vger.kernel.org
Subject: Re: Enable SCTERC in the kernel?
Date: Fri, 25 Oct 2013 21:42:52 +1100 [thread overview]
Message-ID: <20131025214252.1929c7f1@notabene.brown> (raw)
In-Reply-To: <1969984.qn2lKzvFd6@eseries.newtech.fi>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Fri, 25 Oct 2013 11:51 +0300 Dag Nygren <dag@newtech.fi> wrote:
>
> Hi all!
>
> Just run into the standard problem by not having SCTERC enabled
> for my drives due to a spelling mistake in my rc.local script
> setting the parameters and started wondering:
>
> - What if the md module automatically set this during assembly
> of the RAID? - In the kernel module itself. It could always set it,
> if the set failed we could spit out a kernel warning that the used
> drive might not be the best as a RAID device. Would there be any ill
> effects from this?
> - And ditto for the device time-out.
>
> This would definitely make md work a lot better for people. I have a
> strange feeling that most don't know the parameter needs setting...
I don't think it is appropriate for the kernel to automatically set such
things. However it might be appropriate for mdadm to do it when assembling
or creating the array.
I'm happy to review and possibly accept patches.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-10-25 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 8:51 Enable SCTERC in the kernel? Dag Nygren
2013-10-25 10:42 ` NeilBrown [this message]
2013-10-25 12:29 ` Phil Turmel
2013-10-25 16:29 ` Piergiorgio Sartor
2013-10-25 10:47 ` Martin K. Petersen
2013-10-25 11:10 ` Dag Nygren
2013-10-25 11:27 ` Martin K. Petersen
2013-10-25 11:35 ` Dag Nygren
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=20131025214252.1929c7f1@notabene.brown \
--to=neilb@suse.de \
--cc=dag@newtech.fi \
--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).