Bug 2256581
| Summary: | mds:scrub repair does not clear earlier damage health status | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Neeraj Pratap Singh <neesingh> |
| Component: | CephFS | Assignee: | Neeraj Pratap Singh <neesingh> |
| Status: | CLOSED ERRATA | QA Contact: | Hemanth Kumar <hyelloji> |
| Severity: | medium | Docs Contact: | Rivka Pollack <rpollack> |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | ceph-eng-bugs, cephqe-warriors, gfarnum, rpollack, sumr, tserlin, vshankar |
| Target Milestone: | --- | ||
| Target Release: | 7.1z8 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-18.2.1-343.el9cp | Doc Type: | Bug Fix |
| Doc Text: |
.`scrub repair` command now clears `HEALTH_ERR` outputs
Previously, the `scrub repair` command did not clear damage entries flagged as `HEALTH_ERR` when running the `scrub recursive` command.
With this fix, the `scrub repair` command now properly clears the affected `HEALTH_ERR` entries, ensuring that damage is resolved and no longer appears in the output.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-09-30 15:02:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity. Neeraj, please post a downstream MR. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Ceph Storage 7.1 security and bug fix updates), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2025:17059 |
Description of problem: "ceph tell mds.0 scrub start ~mdsdir recursive" finds one backtrace error (putting the cluster into HEALTH_ERR). Even after doing repair which according to the log did rewrite the inode, and subsequent scrubs have not found it. However the cluster health is still ERR, and the MDS still shows the damage: ceph@xxxx1:~$ ceph tell mds.0 damage ls 2022-03-12T18:42:01.609+0000 7f1b817fa700 0 client.173985213 ms_handle_reset on v2:192.168.80.121:6824/939134894 2022-03-12T18:42:01.625+0000 7f1b817fa700 0 client.173985219 ms_handle_reset on v2:192.168.80.121:6824/939134894 [ { "damage_type": "backtrace", "id": 3308827822, "ino": 256, "path": "~mds0" } ] Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: