Bug #40283
closedqa: add testing for lazyio
0%
Description
I'm distressed we have no tests for client behavior (via libcephfs) with lazyio. : /
In particular, verify behavior with two libcephfs instances that it works as expected. In particular, this sequence would be a good first step:
- open two libcephfs instances
- open same file lazyio on both clients
- [client a] write some data, lazyio_propagate/fsync
- [client b] overwrite some data, lazio_propagate/fsync
- [client a] verify with a read that the data has not changed (its cache is stale)
- [client a] lazyio_synchronize
- [client a] verify client b's writes are visible
Updated by Patrick Donnelly almost 5 years ago
- Related to Bug #40284: kclient: evaluate/fix/add lazio support in the kernel added
Updated by Patrick Donnelly almost 5 years ago
- Assignee changed from Siddharth Sharma to Sidharth Anupkrishnan
Wrong Sidharth, sorry!
Updated by Sidharth Anupkrishnan almost 5 years ago
- Status changed from New to In Progress
- Pull request ID set to 28834
Updated by Sidharth Anupkrishnan over 4 years ago
- Status changed from In Progress to Fix Under Review
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to nautilus,mimic
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42161: nautilus: qa: add testing for lazyio added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42162: mimic: qa: add testing for lazyio added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".