[Bugs] [Bug 1224196] New: Disperse volume: Transport endpoint not connected in nfs log messages though the volume is started

bugzilla at redhat.com bugzilla at redhat.com
Fri May 22 10:16:24 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1224196

            Bug ID: 1224196
           Summary: Disperse volume: Transport endpoint not connected in
                    nfs log messages though the volume is started
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: disperse
          Keywords: Triaged
          Assignee: rhs-bugs at redhat.com
          Reporter: byarlaga at redhat.com
        QA Contact: byarlaga at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    byarlaga at redhat.com, gluster-bugs at redhat.com,
                    pkarampu at redhat.com
        Depends On: 1217322
            Blocks: 1186580 (qe_tracker_everglades)
             Group: redhat



+++ This bug was initially created as a clone of Bug #1217322 +++

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.

--- Additional comment from Bhaskarakiran on 2015-04-30 02:16:19 EDT ---


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1217322
[Bug 1217322] Disperse volume: Transport endpoint not connected in nfs log
messages though the volume is started
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=JCPCxggA33&a=cc_unsubscribe


More information about the Bugs mailing list