On Mon, 16 Feb 2009 12:12:56 +0900 Tejun Heo <tj@xxxxxxxxxx> wrote: > > > > Mmm.. I think it is the SD_TIMEOUT value, defined in drivers/scsi/sd.h > > which currently uses (30 * HZ) as the timeout for most things, > > including for cache flushes. > > > > Try changing it to (180 * HZ) just for fun. > > Yeap, SD_TIMEOUT should be it. But I've never personally seen disk > flushing taking as long as 30 seconds. Does it really happen? It's > not like the drive would be doing random seeking. One full stroke > across the platter should be it. Even with the rotational delay, > going over 30 seconds doesn't seem very likely. I just noticed that the other drive, a Western Digital, was using 1.5Gbps instead of 3.0. So I forced the Samsung to the slower speed and now I can't make the timeout happen anymore. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
