[Gluster-users] Quick way to fix stale gfids?

[Diego Zuccato]

Hello all.

I've had one of the 3 nodes serving a "replica 3 arbiter 1" down for 
some days (apparently RAM issues, but actually failing mobo).
The other nodes have had some issues (RAM exhaustion, old problem 
already ticketed but still no solution) and some brick processes 
coredumped. Restarting the processes allowed the cluster to continue 
working. Mostly.

After the third server got fixed I started a heal, but files didn't get 
healed and count (by "ls -l 
/srv/bricks/*/d/.glusterfs/indices/xattrop/|grep ^-|wc -l") did not 
decrease over 2 days. So, to recover I copied files from bricks to temp 
storage (keeping both copies of conflicting files with different 
contents), removed files on bricks and arbiters, and finally copied back 
from temp storage to the volume.

Now the files are accessible but I still see lots of entries like
<gfid:57e428c7-6bed-4eb3-b9bd-02ca4c46657a>

IIUC that's due to a mismatch between .glusterfs/ contents and normal 
hierarchy. Is there some tool to speed up the cleanup?

Tks.

-- 
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786