Re: Ceph Erasure Coding - Stored vs used

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

 



Den ons 12 feb. 2020 kl 12:58 skrev Kristof Coucke <kristof.coucke@xxxxxxxxx
>:

> For one of my pools I have 107TiB STORED and 298TiB USED.
> This is strange, since I've configured erasure coding (6 data chunks, 3
> coding chunks).
> So, in an ideal world this should result in approx. 160.5TiB USED.
>
> There are 473+M objects stored. Lot's of these files are pretty small.
> (Read 150kb files). Not all of them though.
>
> I suspect that the stripe size is related with this issue. This is still
> the default (4MB), but I am not sure.
>

I seem to recall something about EC not "working" as expected when your
files/objects are smaller than some predefined size, in which case it will
not make the 6+3 split for you.

It would be silly to have a 6-byte object split into 1-byte parts, so in
such cases I think it becomes repl=6 or repl=9 (for 6+3 profiles) or
something which could explain your experience.

-- 
May the most significant bit of your life be positive.
_______________________________________________
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