Project

General

Profile

Actions

Bug #43598

closed

mds: PurgeQueue does not handle objecter errors

Added by Patrick Donnelly over 4 years ago. Updated almost 4 years ago.

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

0%

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

Description

Here: https://github.com/ceph/ceph/blob/6ea89e01971462432e0bc8b128b950acec4d85fe/src/mds/PurgeQueue.cc#L555

The filer may be throwing errors like ENOSPC which are getting ignored. The PurgeQueue may be marking items purged (in the MDS journal) even though nothing has been purged.


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #45602: nautilus: mds: PurgeQueue does not handle objecter errorsResolvedWei-Chung ChengActions
Copied to CephFS - Backport #45603: octopus: mds: PurgeQueue does not handle objecter errorsResolvedWei-Chung ChengActions
Actions #1

Updated by Patrick Donnelly over 4 years ago

  • Target version changed from v15.0.0 to v16.0.0
Actions #2

Updated by Varsha Rao about 4 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Varsha Rao about 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 34144
Actions #4

Updated by Nathan Cutler almost 4 years ago

  • Backport changed from nautilus,mimic to octopus,nautilus
Actions #5

Updated by Patrick Donnelly almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #6

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #45602: nautilus: mds: PurgeQueue does not handle objecter errors added
Actions #7

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #45603: octopus: mds: PurgeQueue does not handle objecter errors added
Actions #8

Updated by Nathan Cutler almost 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".

Actions

Also available in: Atom PDF