Michael van Elst <[email protected]> wrote: > >Basically, if we have N pending VOP_FSYNC for a given filesystem, all > >theses requests will be honoured on first flush, but they are serialized > >and will be acknowledged one by one, with the cost of a useless flush > >each time. Am I right? > > That should be trivial to fix then. Don't flush if it isn't dirty.
Here are the backtrace I collected for ine of the many stuck process waiting for I/O: turnstile_block rw_vector_enter wapbl_begin ffs_write VOP_WRITE nfsrv_write nfssvc_nfsd sys_nfssvc syscall We would add a we_dirty flag to struct wapbl_entry? When would it be set to 1? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz [email protected]
