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@xxxxxxxxxxxxxxxxx] Sent: dinsdag 11 november 2008 19:28 To: Kit Gerrits Cc: dgilbert@xxxxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx 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/ -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
