[Bugs] [Bug 1217322] New: Disperse volume: Transport endpoint not connected in nfs log messages though the volume is started
bugzilla at redhat.com
bugzilla at redhat.com
Thu Apr 30 06:13:28 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1217322
Bug ID: 1217322
Summary: Disperse volume: Transport endpoint not connected in
nfs log messages though the volume is started
Product: GlusterFS
Version: mainline
Component: disperse
Assignee: bugs at gluster.org
Reporter: byarlaga at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
======================
NFS logs are filled with transport endpoint not connected messaged though the
volume is started and mounted on client. IO is getting run from the client and
if the brick goes down and comes up seeing these messages.
Version-Release number of selected component (if applicable):
=============================================================
[root at vertigo ~]# gluster --version
glusterfs 3.8dev built on Apr 28 2015 14:47:20
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
[root at vertigo ~]#
How reproducible:
=================
100%
Steps to Reproduce:
1. Create a distributed disperse volume 2x(8+4) and nfs mount on client
2. Run IO and while its going on bring down the bricks.
3. Bring the bricks up with volume start force and check the nfs logs.
Actual results:
==============
Transport end point not connected messages
Expected results:
Additional info:
===============
Attaching the NFS logs of server.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list