Actions
Bug #15912
closedAn OSD was seen getting ENOSPC even with osd_failsafe_full_ratio passed
Status:
Resolved
Priority:
Urgent
Assignee:
David Zafman
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
kraken, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The value of osd_failsafe_full_ratio only restricts new client ops by default after 97% full condition. Could it be that an OSD with large journal could have enough pending filestore data updates that the 3% isn't enough to absorb those updates?
Should new client operations be restricted based on journal size? We could make the value of osd_failsafe_full_ratio an over-ride with default to 0 (use computed value).
Updated by David Zafman almost 8 years ago
Potentially backfill or recovery used the remaining space.
Updated by David Zafman about 7 years ago
https://github.com/ceph/ceph/pull/13425
There are multiple issues to address. This pull requests addresses some of them.
Updated by Nathan Cutler about 7 years ago
- Related to Bug #16878: filestore: utilization ratio calculation does not take journal size into account added
Updated by David Zafman about 7 years ago
- Related to Bug #18687: bluestore: ENOSPC writing to XFS block file on smithi added
Updated by David Zafman about 7 years ago
- Related to deleted (Bug #16878: filestore: utilization ratio calculation does not take journal size into account)
Updated by David Zafman about 7 years ago
- Related to Bug #16878: filestore: utilization ratio calculation does not take journal size into account added
Updated by David Zafman about 7 years ago
- Status changed from New to Resolved
Updated by David Zafman about 7 years ago
- Status changed from Resolved to Pending Backport
- Backport set to kraken, jewel
Updated by David Zafman about 7 years ago
- Related to Feature #15910: Increase the default value of mon_osd_min_in_ratio added
Updated by Alexey Sheplyakov about 7 years ago
- Copied to Backport #19265: jewel: An OSD was seen getting ENOSPC even with osd_failsafe_full_ratio passed added
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19340: kraken: An OSD was seen getting ENOSPC even with osd_failsafe_full_ratio passed added
Updated by David Zafman almost 7 years ago
- Related to Bug #19682: Additional full fixes added
Updated by David Zafman almost 7 years ago
- Related to Bug #19698: cephtool/test.sh error on full tests added
Updated by David Zafman almost 7 years ago
We should backport the 2 trackers/pulls in this order:
Updated by David Zafman almost 7 years ago
- Related to deleted (Bug #19698: cephtool/test.sh error on full tests)
Updated by David Zafman almost 7 years ago
- Related to Bug #19733: clean up min/max span warning added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions