SUBJ. Found by code inspection and confirmed by looking at blktrace data.
Thank you very much creating this bug with a pending fix. Please, if can, justify why this is a rather bug than enhancement and how severe it would be for customers not having this fix. 2.0.1 is pretty much locked down only for blockers. Thanks much.
Per email discussions and bug scrubs, moving this to 2.0.2 list for now. Candidate for a hotfix if turns out to be a common issue for users. Thanks.
couchstore folks are going to fix that as part of switching to single fsync per commit
refer to CBD-818