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.
Created attachment 1020416 [details] nfs logs
In latest releases, this bug doesn't happen. Closing this.
This bug is getting closed because iyt is not reproducible. In case the problem is still not fixed, please open a new bug report.