From: Stan Hoeppner <stan@hardwarefreak.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: "blocked for more than 120 secs" --> a valid situation, how to prevent?
Date: Thu, 23 Sep 2010 19:51:48 -0500 [thread overview]
Message-ID: <4C9BF624.7090906@hardwarefreak.com> (raw)
In-Reply-To: <4C9BE5A8.1090002@teksavvy.com>
Mark Lord put forth on 9/23/2010 6:41 PM:
> What's the purpose of this stack dump,
> and how can it be prevented in this NORMAL situation??
>
> The command was "hdparm --security-erase NULL /dev/sdb",
> which takes about 66 minutes to complete on this particular drive.
>
> I don't see any obvious way for the task to mark itself
> as needing longer than 120 secs to complete the operation.
~$ man hdparm
ATA Security Feature Set
These switches are DANGEROUS to experiment with,
and might not work with every kernel. USE AT YOUR OWN RISK.
--security-erase PWD
THIS FEATURE IS EXPERIMENTAL AND NOT WELL TESTED. USE AT YOUR
OWN RISK.
--
Stan
next prev parent reply other threads:[~2010-09-24 0:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 23:41 "blocked for more than 120 secs" --> a valid situation, how to prevent? Mark Lord
2010-09-24 0:05 ` Douglas Gilbert
2010-09-24 2:53 ` Mark Lord
2010-09-24 3:51 ` Mark Lord
2010-09-24 9:12 ` Jens Axboe
2010-09-24 13:51 ` [PATCH] block: Prevent hang_check firing during long I/O Mark Lord
2010-09-24 13:52 ` Jens Axboe
2010-09-24 4:41 ` "blocked for more than 120 secs" --> a valid situation, how to prevent? Douglas Gilbert
2010-09-24 0:51 ` Stan Hoeppner [this message]
2010-09-24 1:37 ` Kyle McMartin
2010-09-24 3:48 ` Stan Hoeppner
2010-09-24 5:02 ` Douglas Gilbert
2010-09-24 5:31 ` Mark Lord
2010-09-24 6:22 ` Stan Hoeppner
2010-09-24 6:30 ` hdparm-9.32 released: recommended upgrade Mark Lord
2010-09-24 1:58 ` "blocked for more than 120 secs" --> a valid situation, how to prevent? Maxim Levitsky
2010-09-24 2:08 ` Kyle McMartin
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=4C9BF624.7090906@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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