[Gluster-users] NFS crashes - bug 1010241

Shawn Heisey gluster at elyograg.org
Wed Nov 19 16:41:35 UTC 2014

We are running into this crash stacktrace on 3.4.2.


The NFS process dies with no predictability.  I've written a shell
script that detects the crash and runs a process to completely kill all
gluster processes and restart glusterd, which has eliminated
customer-facing fallout from these problems.

Because of continual stability problems from day one, the gluster
storage is being phased out, but there are many terabytes of data still
used there.  It would be nice to have it remain stable while we still
use it.  As soon as we can fully migrate all data to another storage
solution, the gluster machines will be decommissioned.

That BZ id is specific to version 3.6, and it's always difficult for
mere mortals to determine which fixes have been backported to earlier

Has the fix for bug 1010241 been backported to any 3.4 release?  If so,
is it possible for me to upgrade my servers without being concerned
about the distributed+replicated volume going offline?  When we upgraded
from 3.3 to 3.4, the volume was not fully functional as soon as we
upgraded one server, and did not become fully functional until all
servers were upgraded and rebooted.

Assuming again that there is a 3.4 version with the fix ... the gluster
peers that I use for NFS do not have any bricks.  Would I need to
upgrade ALL the servers, or could I get away with just upgrading the
servers that are being used for NFS?


More information about the Gluster-users mailing list