Project

General

Profile

Actions

Bug #13840

closed

Ceph Pools' MAX AVAIL is 0 if some OSDs' weight is 0

Added by Chengyuan Li over 8 years ago. Updated about 8 years ago.

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

0%

Source:
other
Tags:
Backport:
hammer, infernalis
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

After adding a new OSD and set its weight to 0, the pools' MAX AVAIL becomes 0 in "ceph df".

  1. ceph df
    GLOBAL:
    SIZE AVAIL RAW USED %RAW USED
    14694G 14694G 202M 0
    POOLS:
    NAME ID USED %USED MAX AVAIL OBJECTS
    rbd 0 0 0 0 0
    test2 1 0 0 0 0
    cephfs_data 2 0 0 0 0
    cephfs_metadata 3 2344 0 0 20
    cephfs2_data 4 0 0 0 0
    cephfs2_metadata 5 0 0 0 0
    rbd2 6 0 0 0 0

Related issues 3 (0 open3 closed)

Related to Ceph - Bug #10257: Ceph df doesn't report MAX AVAIL correctly when using rulesets and OSD in ruleset is down and outResolvedJoao Eduardo Luis12/05/2014

Actions
Copied to Ceph - Backport #13929: infernalis: Ceph Pools' MAX AVAIL is 0 if some OSDs' weight is 0ResolvedAbhishek VarshneyActions
Copied to Ceph - Backport #13930: hammer: Ceph Pools' MAX AVAIL is 0 if some OSDs' weight is 0ResolvedNathan CutlerActions
Actions

Also available in: Atom PDF