[Gluster-devel] .glusterfs directory?

Ravishankar N ravishankar at redhat.com
Tue Dec 22 05:43:39 UTC 2020

On 21/12/20 2:35 pm, Emmanuel Dreyfus wrote:
> On Mon, Dec 21, 2020 at 01:53:06PM +0530, Ravishankar N wrote:
>> Are you talking about the entries inside.glusterfs/indices/xattrop/* ? Any
>> stale entries here should automatically be purged when self-heal daemon as
>> it crawls the folder periodically.
> I mean for instance:
> # ls -l .glusterfs/aa/aa/aaaadd69-7b3d-45e9-bd0f-8a8bbaa189a5
> lrwxrwxrwx  1 root  wheel  60 Nov  4  2018 .glusterfs//aa/aa/aaaadd69-7b3d-45e9-bd0f-8a8bbaa189a5 -> ../../f0/91/f091de81-a4e2-4548-acf4-4b19c7bdac5e/tpm_nvwrite
> # ls -l .glusterfs/f0/91/f091de81-a4e2-4548-acf4-4b19c7bdac
> ls: .glusterfs/f0/91/f091de81-a4e2-4548-acf4-4b19c7bdac5e/tpm_nvwrite: No such file or directory

If this is the case on all bricks, then it might be okay to remove this 
stale symlink. But if tpm_nvwrite directory is present on other bricks, 
then it is better to check what the path to it is [1] and if its 
trusted.gfid xattr is indeed aaaadd69-7b3d-45e9-bd0f-8a8bbaa189a5 and 
why its missing on this brick alone (maybe pending self heal?)



More information about the Gluster-devel mailing list