Description of problem: When IProcessClient.writefile() returns, the write was completed, but the data may be in the host page cache instead of storage. Other hosts will see stale data until the kernel write the dirty pages to storage. If the storage becomes non responsive, or a fatal error occur, some or all of the data may be lost. Callers of this method in vdsm assume that the data was transferred to storage, and other hosts can see the data once writefile returned successfully. Version-Release number of selected component (if applicable): Any How reproducible: Always Steps to Reproduce: 1. Run ioprocess with strace -f 2. Call IOProcessClinet.writefile() Actual results: In strace output we see that ioprocess doe snot call fsync on the file descriptor. Expected results: ioprocess should call fsync() before returning.
Tal, this is very bad issue in storage infrastructure, there is no way we can defer this to 4.3. Since we have an approved and tested trivial fix, suggesting for 4.2.1.
ioprocess-1.0.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbe8141dd2
ioprocess-1.0.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbe8141dd2
ioprocess-1.0.2-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5fc2a37e8a
ioprocess-1.0.2-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-5fc2a37e8a
Full tier1 automation ran using ioprocess-1.0.2-1.el7ev.x86_64, no errors or regressions occurred related to the new ioprocess. moving to verify.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.
ioprocess-1.0.2-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.