From: "Kit Gerrits" <kitgerrits@gmail.com>
To: 'Stefan Richter' <stefanr@s5r6.in-berlin.de>
Cc: dgilbert@interlog.com, linux-scsi@vger.kernel.org
Subject: RE: Question about spun-down USB disk
Date: Tue, 11 Nov 2008 20:07:01 +0100 [thread overview]
Message-ID: <4919d7d8.188d420a.4772.10b1@mx.google.com> (raw)
In-Reply-To: <4919CE9F.80304@s5r6.in-berlin.de>
OK, that is odd.
The timer on all my disks report 60 (I assume those are seconds).
I'll keep an eye out for that error and see if I can find out where it came
from.
If it is not the spin-up time, I must have accidentally pulled a (USB)
cable.
(From what I can see in the logs, I just plugged in a different drive before
the drive failed)
I thank you very much for the hint, it was exactly what I was looking for,
and I apologoze for my <rant> from earlier on.
(I assumed it was set to 1 or 5 seconds).
Regards,
Kit Gerrits
-----Original Message-----
From: Stefan Richter [mailto:stefanr@s5r6.in-berlin.de]
Sent: dinsdag 11 november 2008 19:28
To: Kit Gerrits
Cc: dgilbert@interlog.com; linux-scsi@vger.kernel.org
Subject: Re: Question about spun-down USB disk
Kit Gerrits wrote:
...
> If, for some reason, a program wants to write to a file on there
> without spinning the drive up in advance, the error pops up.
> Mind you, I haven't had the error in days now.
>
> All I'm looking for is a way to increase the time the O/S waits for
> the disk to spin up.
Try the /sys/bus/scsi/devices/*:*:*:*/timeout attribute.
Of course increasing the timeout isn't a particularly sophisticated method
to solve the issue, but simple enough to try. The default timeout is 30
seconds: linux/drivers/scsi/sd.h::SD_TIMEOUT. Can an HDD really take longer
than that to receive a request when spun down, spin up, execute the request,
and return status?
--
Stefan Richter
-=====-==--- =-== -=-==
http://arcgraph.de/sr/
prev parent reply other threads:[~2008-11-11 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 21:41 Question about spun-down USB disk Kit Gerrits
2008-11-09 22:36 ` Douglas Gilbert
2008-11-10 2:17 ` Kit Gerrits
2008-11-10 17:01 ` Stefan Richter
2008-11-11 0:11 ` Kit Gerrits
2008-11-11 18:27 ` Stefan Richter
2008-11-11 19:07 ` Kit Gerrits [this message]
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=4919d7d8.188d420a.4772.10b1@mx.google.com \
--to=kitgerrits@gmail.com \
--cc=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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.