Hi Xavi,
Thanks for the quick reply! Maybe I should explain better my motivation for the above mentioned experiments. I have a large production system running GlusterFS with almost 5 PB of data (in approx 100G of inodes). It's a distributed-only system (no sharding, not dispersed). In this system, the users sometimes experience the problem that they cannot delete a seemingly empty directory. The cause of this problem is, that the directory contains leftover link files, i.e. dht link files where the target is gone. I haven't identified yet why this happens and I don't have a method to provoke this error (otherwise I would have mentioned it on this list already.) But my quick & dirty fix is, to delete these leftover link files by hand. (These leftover link files are not being cleaned up by a "rebalance".) The reason for my experiments with link files is: what happens if for some reason I accidentally delete a link file where the target still exists? In the experiments (not on the production system) I also tried umounting and remounting the system, and I already tried setting "loopup-optmize = off". It doesn't affect the outcome of the experiments. best wishes, Stefan |
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users