[Gluster-users] NFS client blocking reboot
haiwei.xie at soulinfo.com
Fri Jul 26 06:44:34 UTC 2013
A node: nfs client, mount B gluster native nfs server.
B/C node: gluster nodes, replica 2 volume.
version: 3.3.1 release.
A node: cp big data into nfs dir.
B node: poweroff.
C node: server_connection_destroy with client B --> server_connection_get with client B.
Why C node call server_connection_get with client B again, and successfully. Actually, B was already poweroff.
Maybe this is a bug?
> On Thu, 25 Jul 2013 14:52:19 +0200
> Marcus Bointon <marcus at synchromedia.co.uk> wrote:
> > This is a silly chicken-and-egg problem. I've found when I issue a reboot on a server that's mounted its own gluster volume via NFS (with the 'hard' option set), it stops gluster before unmounting volumes. This causes the NFS client to hang waiting for a response from the gluster server (which will never happen because it's stopped), blocking the reboot, leaving the server hanging indefinitely. The only way out seems to be to power-cycle the server.
> > How is this supposed to work? Is there some way of scheduling unmounts before killing gluster?
> > Marcus
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://supercolony.gluster.org/mailman/listinfo/gluster-users
> It's interesting. My experience, if you mount nfs on other computer, poweroff gluster node, your nfs client will hang too.
> It looks like bug of gluster native nfs server. Maybe some masters can explain the reason.
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users