Hello, Chuck Ebbert wrote: >> 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. Timeouts are much more likely with the higher transfer speed but it's kind of strange for flush cache to be affected by it as the command doesn't have any data to transfer. :-( -- tejun -- 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
