Bug 870018

Summary:	Kernel 3.6.2 MTU problem with GlusterFS in multiple machines
Product:	[Fedora] Fedora	Reporter:	Eduardo <activepage>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
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:	2013-02-13 15:43:16 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:

Description Eduardo 2012-10-25 12:01:33 UTC

I have several server in Virtualized and Normal Servers Running Fedora and GlusterFS 3.2.7.

Yesterday I Update 9 Machines to the last Fedora Kernel 3.6.2.

After the Upgrade all the 9 Machines the gluster Client stop working and Can´t connect with the servers.

On all Machines I use a MTU 6000, if a change back to 1500, the gluster start to work, but if I set the MTU to 6000, the gluster client don´t work.

I have diferente Hardware and NetworkCards Intel, Realtek and in Virtualized use Virtio, all with the problem with MTU.

On all machines I have to use the old kernel 3.4.7, and everything works perfectly, with MTU 6000.

Bellow just the error of gluster:
[2012-10-25 09:40:02.367285] W [socket.c:1494:__socket_proto_state_machine] 0-client-1: reading from socket failed. Error (Connection reset by peer), peer (xx.xxx.xxx.x:24016)
[2012-10-25 09:40:02.367350] E [rpc-clnt.c:341:saved_frames_unwind] (-->/usr/lib64/libgfrpc.so.0(rpc_clnt_notify+0xa0) [0x3f8240f5e0] (-->/usr/lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x7d) [0x3f8240f28d] (-->/usr/lib64/libgfrpc.so.0(saved_frames_destroy+0xe) [0x3f8240f1ee]))) 0-client-1: forced unwinding frame type(GF-DUMP) op(DUMP(1)) called at 2012-10-25 09:38:19.472337
[2012-10-25 09:40:02.367363] W [client-handshake.c:1273:client_dump_version_cbk] 0-client-1: received RPC status error
[2012-10-25 09:40:02.367374] I [client.c:1883:client_rpc_notify] 0-client-1: disconnected

Comment 1 Fedora End Of Life 2013-01-16 14:34:16 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 15:43:19 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.