Re: Unintuitive (buggy?) CephFS behaviour when dealing with pool_namespace layout attribute

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

 



Hi,


just some assumptions based on my experience with cephfs:

- you cannot change existing objects; setting a different pool will not automagically move data. the data pool seems to be stored in the inode information

- this also explains why changing the pool of a file does not work. ceph is unable to move the data on its own

- so after changing the pool for a directory, all existing files will remain in their original pool

- only newly created files will inherit the changed pool assignment

- moving a file does not create a new inode, so its pool assignment cannot be changed by moving


The last time we want to perform a large scale pool change we had to copy each file / directory to actually move the data.


Best regards,

Burkhard Linke

_______________________________________________
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