Project

General

Profile

Actions

Bug #12401

closed

pgmonitor: wrong "at/near target max“ reporting

Added by huang jun almost 9 years ago. Updated over 8 years ago.

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

0%

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

Description

we set pool's target_max_bytes to 89000000000000(89TB),
but when the pool use 29561632420936B,
the "ceph health detail" reports "cache pool 'myEC1-autocache' with 27531GB at/near target max 82887GB"
after add some extra output info, we get this:
2015-07-20 09:40:48.704394 7f623868e700 0 mon.lab8101@0(leader).pg v357987 cache pool 'myEC1-autocache' with 29561632420936B at/near target max 89000000000000B ratio 932000 cache_target_full_ratio_micro 800000 mon_cache_target_full_warn_ratio 0.66 target_max_bytes*ratio/1000000 9161023705161

it seems the uint64_t can not hold "89000000000000*932000" which large than 2^64;


Related issues 2 (0 open2 closed)

Copied to Ceph - Backport #12495: pgmonitor: wrong "at/near target max“ reportingResolvedNathan Cutler07/20/2015Actions
Copied to Ceph - Backport #12496: pgmonitor: wrong "at/near target max“ reportingResolvedLoïc Dachary07/20/2015Actions
Actions

Also available in: Atom PDF