It seems that if I manually delete the problem file/directory from each brick directly, the problem goes away. I'm still wondering what caused this, and how to avoid it in production. Michael On 07/09/2013 10:35 AM, Michael Peek wrote: > Hello Gluster gurus, > > I'm experimenting with Gluster and I've run across a problem that I > don't understand. > > I have Ubuntu 12.04 with Gluster 3.2.5. I created a volume and filled > it with data. Then I left an rm -fr going to wipe it out over night. > When I came in this morning, I found a lot of stuff like this: > > rm: cannot remove `old/old.5/test-host/20130707/etc/init.d/apport': > Stale NFS file handle > > The log file data-testvol.log shows: > > [2013-07-09 10:13:37.229796] W [stat-prefetch.c:2632:sp_unlink_helper] > 0-testvol-stat-prefetch: lookup-behind has failed for path > (/old/old.5/test-host/20130707/etc/init.d/apport)(Stale NFS file > handle), unwinding unlink call waiting on it > [2013-07-09 10:13:37.229811] W [fuse-bridge.c:911:fuse_unlink_cbk] > 0-glusterfs-fuse: 105965: UNLINK() > /old/old.5/test-host/20130707/etc/init.d/apport => -1 (Stale NFS file > handle) >
