Bug 2041572
| Summary: | mds: fails to reintegrate strays if destdn's directory is full (ENOSPC) | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Patrick Donnelly <pdonnell> |
| Component: | CephFS | Assignee: | Venky Shankar <vshankar> |
| Status: | CLOSED ERRATA | QA Contact: | Hemanth Kumar <hyelloji> |
| Severity: | low | Docs Contact: | Akash Raj <akraj> |
| Priority: | low | ||
| Version: | 5.1 | CC: | akraj, ceph-eng-bugs, sostapov, tserlin, vereddy, vshankar |
| Target Milestone: | --- | ||
| Target Release: | 5.1z2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.7-121.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.Reintegrating stray entries does not fail when the destination directory is full
Previously, Ceph Metadata Servers reintegrated an unlinked file if it had a reference to it, that is, if the deleted file had hard links or was a part of a snapshot. The reintegration, which is essentially an internal rename operation, failed if the destination directory was full. This resulted in Ceph Metadata Server failing to reintegrate stray or deleted entries.
With this release, full space checks during reintegrating stray entries are ignored and these stray entries are reintegrated even when the destination directory is full.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-06-30 20:54:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2099589 | ||
|
Description
Patrick Donnelly
2022-01-17 18:00:18 UTC
Hi Akash, PTAL at the doc text. 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 5.1 Bug Fix update), 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-2022:5450 |