From: Erwan Velu <erwanaliasr1@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Question about the maximum value for unload_head
Date: Wed, 02 Jun 2010 22:46:59 +0200 [thread overview]
Message-ID: <4C06C343.3050903@gmail.com> (raw)
Hey folks,
I'm in an industrial situation where my Linux system could be strongly
shacked for some minutes.
I'm able to detect this situation and so, to protect my hard drive, I
park its heads by using the unload_heads feature.
I have nothing to say more than it works sooooo good ! But I saw there
is a limitation to 30sec as #define MAX_PARK_TIMEOUT 30000
That mean in my case that I have to manage a stupid script that have to
retrigger the unload_heads every 30sec. That's stupid script and I
wonder if it could be possible to get rid of it. Why is there such
limitation. Why 30sec ?
Could it be possible to increase this value ?
Thanks for your inputs,
Erwan Velu
reply other threads:[~2010-06-02 20:47 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=4C06C343.3050903@gmail.com \
--to=erwanaliasr1@gmail.com \
--cc=linux-ide@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).