Bug 1217322

Summary: Disperse volume: Transport endpoint not connected in nfs log messages though the volume is started
Product: [Community] GlusterFS Reporter: Bhaskarakiran <byarlaga>
Component: disperseAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: amukherj, aspandey, bugs, mzywusko, pkarampu
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1224196 (view as bug list) Environment:
Last Closed: 2017-08-11 10:27:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1186580, 1224196    
Attachments:
Description Flags
nfs logs none

Description Bhaskarakiran 2015-04-30 06:13:28 UTC 
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@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@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.
Comment 1 Bhaskarakiran 2015-04-30 06:16:19 UTC 
Created attachment 1020416 [details]
nfs logs
Comment 3 Pranith Kumar K 2015-09-18 03:06:04 UTC 
In latest releases, this bug doesn't happen. Closing this.
Comment 5 Ashish Pandey 2017-08-11 10:27:22 UTC 
This bug is getting closed because iyt is not reproducible. In case the problem is still not fixed, please open a new bug report.