Comment 6 for bug 1709889

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-08-15 09:32 EDT-------
I should also add that the data indicates there is an instability to the delay, with the initial stalled I/Os maxing out at about 70 seconds, then the next cycle (~10 hours later) and subsequent 2 shows max values in the 90-100 second range, and the following 5 cycles show numbers around 110 seconds (but tapering off). I think this unpredictability is further indication of a bug in CFQ. Clearly it does not live up to it's name, at least for these particular I/Os.