Project

General

Profile

Actions

Bug #36370

closed

add information about active scrubs to "ceph -s" (and elsewhere)

Added by Venky Shankar over 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
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

currently, there is no way to track scrubs operations on a filesystem expect to check the mds log and figure out which ones have completed/pending (since multiple scrub operations can be triggered on subpaths).

It would be helpful if the active scrub operations are shown in ceph status output. Sample output can be:

MDS.<daemonID> scrubbing in progress: scrub_path <path_that_is_scrubbed> recursive repair
MDS.<daemonID> scrubbing in progress: scrub_path <different_path_that_is_scrubbed> recursive repair

This would especially simplify situations when multiple scrub_path commands were started or with large cephfs.


Related issues 4 (1 open3 closed)

Related to CephFS - Feature #12282: mds: progress/abort/pause interface for ongoing scrubsResolvedVenky Shankar

Actions
Related to CephFS - Feature #38052: mds: provide interface to control/view internal operationsNew

Actions
Related to Dashboard - Bug #41525: mgr/dashboard: Missing service metadata is not handled correctlyResolvedVolker Theile

Actions
Copied to CephFS - Backport #41508: nautilus: add information about active scrubs to "ceph -s" (and elsewhere)ResolvedVenky ShankarActions
Actions #1

Updated by Venky Shankar over 5 years ago

  • Component(FS) MDS added
Actions #2

Updated by Patrick Donnelly over 5 years ago

  • Related to Feature #12282: mds: progress/abort/pause interface for ongoing scrubs added
Actions #3

Updated by Patrick Donnelly about 5 years ago

  • Target version changed from v14.0.0 to v15.0.0
Actions #4

Updated by Patrick Donnelly about 5 years ago

  • Related to Feature #38052: mds: provide interface to control/view internal operations added
Actions #5

Updated by Patrick Donnelly almost 5 years ago

  • Start date deleted (10/10/2018)
  • Backport set to nautilus

Venky, status on this ticket?

Actions #6

Updated by Venky Shankar almost 5 years ago

Patrick Donnelly wrote:

Venky, status on this ticket?

For this ticket: scrub status commands have been added via tell interface (tracker #12282).

Regarding the backport, IIRC, we decided not to backport this to nautilus.

Actions #7

Updated by Patrick Donnelly almost 5 years ago

Venky Shankar wrote:

Patrick Donnelly wrote:

Venky, status on this ticket?

For this ticket: scrub status commands have been added via tell interface (tracker #12282).

Regarding the backport, IIRC, we decided not to backport this to nautilus.

This ticket is a little different from what we did for ceph tell scrub_*. This one sends a health message to the monitors about what paths are being scrubbed.

Actions #8

Updated by Venky Shankar almost 5 years ago

Patrick Donnelly wrote:

Venky Shankar wrote:

Patrick Donnelly wrote:

Venky, status on this ticket?

For this ticket: scrub status commands have been added via tell interface (tracker #12282).

Regarding the backport, IIRC, we decided not to backport this to nautilus.

This ticket is a little different from what we did for ceph tell scrub_*. This one sends a health message to the monitors about what paths are being scrubbed.

OK -- I kind of assumed (in the email discussions we had) that the `scrub status` command would be the recommended interface. I'll pick this ticket soon...

Actions #9

Updated by Venky Shankar almost 5 years ago

  • Pull request ID set to 28855
Actions #10

Updated by Patrick Donnelly over 4 years ago

  • Status changed from In Progress to Pending Backport
Actions #11

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41508: nautilus: add information about active scrubs to "ceph -s" (and elsewhere) added
Actions #12

Updated by Patrick Donnelly over 4 years ago

  • Related to Bug #41525: mgr/dashboard: Missing service metadata is not handled correctly added
Actions #13

Updated by Nathan Cutler about 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