ceph df: pool stored vs bytes_used -- raw or not?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Depending on which cluster I look at (all running v14.2.11), the
bytes_used is reporting raw space or stored bytes variably.

Here's a 7 year old cluster:

# ceph df -f json | jq .pools[0]
{
  "name": "volumes",
  "id": 4,
  "stats": {
    "stored": 1229308190855881,
    "objects": 294401604,
    "kb_used": 1200496280133,
    "bytes_used": 1229308190855881,
    "percent_used": 0.4401889145374298,
    "max_avail": 521125025021952
  }
}

Note that stored == bytes_used for that pool. (this is a 3x replica pool).

But here's a newer cluster (installed recently with nautilus)

# ceph df -f json  | jq .pools[0]
{
  "name": "volumes",
  "id": 1,
  "stats": {
    "stored": 680977600893041,
    "objects": 163155803,
    "kb_used": 1995736271829,
    "bytes_used": 2043633942351985,
    "percent_used": 0.23379847407341003,
    "max_avail": 2232457428467712
  }
}

In the second cluster, bytes_used is 3x stored.

Does anyone know why these are not reported consistently?
Noticing this just now, I'll update our monitoring to plot stored
rather than bytes_used from now on.

Thanks!

Dan
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux