Project

General

Profile

Bug #40283

qa: add testing for lazyio

Added by Patrick Donnelly 9 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
High
Category:
-
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
libcephfs, qa-suite
Labels (FS):
qa
Pull request ID:
Crash signature:

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


Related issues

Related to fs - Bug #40284: kclient: evaluate/fix/add lazio support in the kernel New
Copied to fs - Backport #42161: nautilus: qa: add testing for lazyio Resolved
Copied to fs - Backport #42162: mimic: qa: add testing for lazyio Rejected

History

#1 Updated by Patrick Donnelly 9 months ago

  • Related to Bug #40284: kclient: evaluate/fix/add lazio support in the kernel added

#2 Updated by Patrick Donnelly 9 months ago

  • Assignee set to Siddharth Sharma

#3 Updated by Patrick Donnelly 9 months ago

  • Assignee changed from Siddharth Sharma to Sidharth Anupkrishnan

Wrong Sidharth, sorry!

#4 Updated by Sidharth Anupkrishnan 8 months ago

  • Status changed from New to In Progress
  • Pull request ID set to 28834

#5 Updated by Sidharth Anupkrishnan 5 months ago

  • Status changed from In Progress to Fix Under Review

#6 Updated by Patrick Donnelly 5 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to nautilus,mimic

#7 Updated by Nathan Cutler 5 months ago

#8 Updated by Nathan Cutler 5 months ago

#9 Updated by Nathan Cutler about 2 months 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".

Also available in: Atom PDF