Bug #3832
closed
client: does not observe O_SYNC
Added by Sage Weil over 11 years ago.
Updated almost 8 years ago.
Description
if the file was opened with O_SYNC we need to flush the io on every write call.
- Assignee set to Sam Lang
- Priority changed from High to Urgent
- Status changed from 12 to Fix Under Review
Implemented in wip-3832. Needs review.
Current status: the iozone-sync.sh test script is causing a segfault (sometimes at hang). Needs more testing! Segfault is at: Context.h:273. Still investigating...
Fixed a bug in objectcacher::flush_set. Branch wip-3832-oc-flushrange has been updated, and passes the accompanying iozone-sync.sh test. Needs final review and merge.
- Status changed from Fix Under Review to Resolved
commit:64b9dd088d8f20019d6c1042895676b2ec57077e
- Component(FS) Client added
Also available in: Atom
PDF