Alasdair G Kergon wrote: > Several kernels releases ago, the implementation of the 'flush device' > operation in the block layer was changed from a simple function call > that dm supported to a mechanism involving barriers that is trickier for > dm to support. Previously 'flush' could not fail and so callers do not > generally have strategies to handle such a situation. The 'caller' here would be fsync() in the FS. What strategies are available to handle a failing 'flush'? It there anything that can be done at application level (userland)? More than anything, does LVM (or device mapper) really reorder writes? Is it safe with disk caches in write-thru mode? (hdparm -W0) .TM. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
