Pranith Kumar Karampuri <pkara...@redhat.com> wrote: > For some reason self-heal on those files must be failing. Wonder why? > Could you find what is the file on the bricks for each of those files > (using find -inum) and give me the getfattr output of those files and > their parent directories please.
Here is the setup: silo:/export/wd2a hangar:/export/wd1a hangar:/export/wd3a debacle:/export/wd1a Example: hangar glustershd loops on: [2013-12-26 05:24:17.113217] W [client-rpc-fops.c:1103:client3_3_getxattr_cbk] 0-gfs351-client-1: remote operation failed: Stale NFS file handle. Path: <gfid:cf1bdf4f-b71c-4fda-963d-b7e4547e1b7c> (cf1bdf4f-b71c-4fda-963d-b7e4547e1b7c). Key: glusterfs.gfid2path I can find silo:/export/wd2a brick looping on [2013-12-26 05:25:39.441290] I [server-rpc-fops.c:154:server_lookup_cbk] 0-gfs351-server: 12899558: LOOKUP (null) (cf1bdf4f-b71c-4fda-963d-b7e4547e1b7c) ==> (Stale NFS file handle) I search .glusterfs/cf/1b/cf1bdf4f-b71c-4fda-963d-b7e4547e1b7c on each bricks: it does not exist anywhere. I tried with other "Stale NFS file handle" messages, and the file never exists in glusterfs index tree. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org _______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel
