Bug 762992 (GLUSTER-1260)

Summary: SETVOLUME force-unwound
Product: [Community] GlusterFS Reporter: Vikas Gorur <vikas>
Component: coreAssignee: Anand Avati <aavati>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: urgent    
Version: 3.0.5CC: amarts, chrisw, gluster-bugs, sac
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Logs with trace none

Description Vikas Gorur 2010-08-02 17:13:33 UTC 
The setup is a 6-node distribute-replicate. It was observed that one of the clients shows only 1/3rd of the total storage. Upon examining the logs it is found that the client keeps connecting and sending SETVOLUME, and gets no response and force-unwinds the op and breaks the connection.

Versions of client and server are the same. No authentication failures (auth is set to *). Restarting the server did not fix the problem. Remounting the client did not fix the problem. Rebooting the client fixed it.

Logs in TRACE attached.
Comment 1 Amar Tumballi 2010-08-03 05:24:25 UTC 
was there any 'firewall' setting which was prevening it? can you please attach logs here? I don't see any attachments in this bug.

-Amar
Comment 2 Sachidananda Urs 2010-08-03 05:37:48 UTC 
Attaching the logs.

Firewall settings:
(In reply to comment #1)
> was there any 'firewall' setting which was prevening it? can you please attach
> logs here? I don't see any attachments in this bug.
> 
> -Amar

calypso:~# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source destination 
calypso:~# iptables -t mangle -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination 

Chain INPUT (policy ACCEPT)
target prot opt source destination 

Chain FORWARD (policy ACCEPT)
target prot opt source destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination 
calypso:~# 

loge:~# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source destination 
loge:~# iptables -t mangle -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination 

Chain INPUT (policy ACCEPT)
target prot opt source destination 

Chain FORWARD (policy ACCEPT)
target prot opt source destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination 
loge:~#
Comment 3 Sachidananda Urs 2010-08-03 05:39:04 UTC 
Created attachment 266 [details]
piranha output upon startup
Comment 4 Anand Avati 2010-10-01 05:17:08 UTC 
Was diagnosed to be a network hardware related issue