We are having the same problem (see my post earlier this week). We have four server nodes in a replicated cluster, and each is providing localhost server facilities. The only comment I have gotten is not to use Gluster for a cache drive, but that doesn't really address the problem of why this is happening. NFS should be able to exclusively lock the files. sean On 03/14/2012 05:52 AM, David Coulson wrote: > I recently moved from the fuse client to NFS - Now I'm seeing a bunch > of this in syslog. Is this something to be concerned about, or is it > 'normal' NFS behavior? > > NFS: server localhost error: fileid changed > fsid 0:15: expected fileid 0xd88ba88a97875981, got 0x40e476ef5fdfbe9f > > I also see a lot of 'stale file handle' in nfs.log, but the timestamps > don't correspond. > > I'm running gluster 3.2.5 on RHEL6. > > David > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > -- Sean Fulton GCN Publishing, Inc. Internet Design, Development and Consulting For Today's Media Companies http://www.gcnpublishing.com (203) 665-6211, x203
