From: rct@gherkin.frus.com (Bob Tracy)
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Kurt Garloff <garloff@suse.de>,
Linux SCSI list <linux-scsi@vger.kernel.org>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Format Unit can take many hours
Date: Tue, 11 May 2004 11:28:22 -0500 (CDT) [thread overview]
Message-ID: <20040511162822.C46BFDBDB@gherkin.frus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0405110952380.14297-100000@sweetums.bluetronic.net> "from Ricky Beam at May 11, 2004 10:01:55 am"
Ricky Beam wrote:
> On Tue, 11 May 2004, Kurt Garloff wrote:
> >the timeout for FORMAT_UNIT should be much longer; I've seen 8hrs
> >already (75Gig). I've increased the timeout from 2hrs to 12hrs.
>
> If you execute a FORMAT_UNIT properly, the timeout is irrelevant. Set the
> IMMED bit so the command returns as soon as the drive begins processing it.
> Send TEST_UNIT_READY to check the progress. I'll have to consult the
> spec, but I think support for Immed is required.
Moreover, it simply "feels" wrong to define a constant for something
that isn't... The quick fix of increasing the timeout doesn't address
the underlying issue of how long a format should take, and as Ricky
implies, that's probably more the concern of the application rather
than the driver.
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next prev parent reply other threads:[~2004-05-11 16:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 11:49 [PATCH] Format Unit can take many hours Kurt Garloff
2004-05-11 12:20 ` Jens Axboe
2004-05-11 12:40 ` Arjan van de Ven
2004-05-11 12:46 ` Jens Axboe
2004-05-11 12:44 ` Kurt Garloff
2004-05-11 16:10 ` Jeff Garzik
2004-05-11 16:14 ` Jens Axboe
2004-05-11 16:26 ` Kurt Garloff
2004-05-11 17:27 ` Jens Axboe
2004-05-11 14:01 ` Ricky Beam
2004-05-11 16:28 ` Bob Tracy [this message]
2004-05-11 16:44 ` Ricky Beam
2004-05-11 18:30 ` Jens Axboe
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=20040511162822.C46BFDBDB@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=garloff@suse.de \
--cc=jfbeam@bluetronic.net \
--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