Hide Forgot
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.
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
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:~#
Created attachment 266 [details] piranha output upon startup
Was diagnosed to be a network hardware related issue