[email protected] (Edgar =?iso-8859-1?B?RnXf?=) writes: >I myself can't make sense out of the combination of >-- vfs.wapbl.flush_disk_cache=0 mitigating the problem >-- neither the RAID set nor its components showing busy in iostat >Maybe during a flush, the discs are not regarded busy?
busy means that the driver is executing I/O requests or waiting for results from such operartions. The cache flush operation doesn't count by itself, but it slows down parallel I/O operations, so the disk appears busy as long as there are such I/O operations.
