Hi, are you using snapshots on CephFS as well? Zitat von Robert Sander via ceph-users <ceph-users@ceph.io>:

Hi,

Am 31.07.26 um 9:11 AM schrieb Dario Graña:

...

here is an snippet from the documentation[0] that explains this behavior: /The data pool used to create the file system is the “default” data pool and the location for storing all inode backtrace information, used for hard link management and disaster recovery. For this reason, all inodes created in CephFS have at least one object in the default data pool. If erasure-coded pools are planned for the file system, it is usually better to use a replicated pool for the default data pool to improve small-object write and read performance for updating backtraces./

Thanks for the hint. I already suspected something like this.

It is so strange as there are many more empty objects in the first replicated data pool than there are "real" file objects in the EC data pool.

Regards -- Robert Sander Linux Consultant

Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: +49 30 405051 - 0 Fax: +49 30 405051 - 19

Amtsgericht Berlin-Charlottenburg - HRB 220009 B Geschäftsführer: Peer Heinlein - Sitz: Berlin _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io