On 05/15/2015 10:16 PM, Niels de Vos wrote: > On Fri, May 15, 2015 at 03:13:52PM +0000, Emmanuel Dreyfus wrote: >> On Fri, May 15, 2015 at 05:07:38PM +0200, Niels de Vos wrote: >>> nfs.disable should be set for all volumes on all your Gluster servers. >> >> /var/lib/glusterd/nfs/nfs-server.vol has option nfs.gfs.disable true >> on all servers. >> >>> If that is indeed done, you should be able to kill the NFS-server. >>> # cat /var/lib/glusterd/nfs/run/nfs.pid | xargs kill >> >> But the NFS server is not started. The problem is that glusterfsd >> tries to talk to it while it is not there. > > Indeed, I just tried it out on a test-system. glusterd tries to talk to > the NFS-server through a local UNIX-socket. And if the NFS-server is > disabled, it continues to fill the logs with warnings about it every 3 > seconds. > > I've filed bug https://bugzilla.redhat.com/1222065 for this. I will take a look at it. In past we have seen readv failure logs in glusterd, need to check whether the root cause is same or not. Will keep you posted. ~Atin > > Niels > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > -- ~Atin _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
