Project

General

Profile

Bug #45575

cephfs-journal-tool: incorrect read_offset after finding missing objects

Added by yantao xue almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

in JournalScanner::scan_events(), read_offset is not increased when find missing objects, that will lead to a wrong result.


Related issues

Copied to CephFS - Backport #46959: octopus: cephfs-journal-tool: incorrect read_offset after finding missing objects Resolved
Copied to CephFS - Backport #46960: nautilus: cephfs-journal-tool: incorrect read_offset after finding missing objects Resolved

History

#1 Updated by Patrick Donnelly over 3 years ago

  • Tracker changed from Fix to Bug
  • Subject changed from tools/cephfs: fix cephfs-journal-tool to cephfs-journal-tool: incorrect read_offset after finding missing objects
  • Status changed from New to Fix Under Review
  • Assignee set to yantao xue
  • Target version set to v16.0.0
  • Source set to Community (dev)
  • Backport set to octopus,nautilus
  • Regression set to No
  • Severity set to 3 - minor
  • Pull request ID set to 35096

#2 Updated by Patrick Donnelly over 3 years ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #46959: octopus: cephfs-journal-tool: incorrect read_offset after finding missing objects added

#4 Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #46960: nautilus: cephfs-journal-tool: incorrect read_offset after finding missing objects added

#5 Updated by Nathan Cutler over 3 years ago

  • Project changed from Ceph to CephFS

#6 Updated by Nathan Cutler over 3 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".

Also available in: Atom PDF