Jeff Garzik wrote:
Mark Lord wrote:
I wonder if it's just a case of too short a timeout on the cache flushes?
The answer in general to this question has always been "yes".....
Unless this has changed in the past year, the worst case for SATA cache
flush can definitely exceed 30 seconds... it is unbounded as defined in
the spec, and unbounded in practice as well.
Of course, users' patience is not unbounded :)
Yeah, it's pretty ludicrous for a cache flush to potentially take that
long. Theoretically if you had a 32MB write cache completely full with
completely non-contiguous sectors you could end up with it taking
something like 2 minutes or more to write out. However, the drive really
should be ensuring that it doesn't build up so much in the write cache
that a flush would takes this long - that is a lot of data that could be
lost on an unexpected power-off.
However, in this case the drive is not reporting Busy status at the
timeout, which suggests maybe an interrupt got lost or something. (Could
be still the drive's fault.)
Chuck, when this happens can you tell if the disk sounds like it is
grinding away until the timeout happens or is it just sitting there?
--
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
