Cephfs default data pool (inode backtrace) no longer a thing?

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

 



Hello

https://docs.ceph.com/en/latest/cephfs/createfs/ mentions a "default data pool" that is used for "inode backtrace information, which is used for hard link management and disaster recovery", and "all CephFS inodes have at least one object in the default data pool".

I noticed that when I create a volume using "ceph fs volume create" and then add the EC data pool where my files actually are, the default pool remains empty (no objects).

Does this mean that the recommendation from the link above "If erasure-coded pools are planned for file system data, it is best to configure the default as a replicated pool" is no longer applicable, or do I need to configure something to avoid a performance hit when using EC data pools?


Thanks

Vlad
_______________________________________________
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