From: Emmanuel Florac <eflorac@intellique.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Hard to debug NFS loss of connectivity: problem solved
Date: Wed, 11 Sep 2013 17:11:45 +0200 [thread overview]
Message-ID: <20130911171145.323f9b9e@harpe.intellique.com> (raw)
In-Reply-To: <20130905191800.1c75b2fb@harpe.intellique.com>
Le Thu, 5 Sep 2013 19:18:00 +0200
Emmanuel Florac <eflorac@intellique.com> écrivait:
> Any hint, idea, etc would be extremely welcome. Even some
> debugging method less painful than digging through huge
> tcpdumps would be nice :)
I post this answer in the faint hope that it may avoid a long and
painful week of testing to someone else :)
The problem comes from the virtual network adapter "Intel pro 1000"
using the e1000e linux driver. The Intel hardware supports a MTU of
4078 max. On a physical machine, it will fail to set up a greater value
with something like:
# ifconfig eth0 mtu 4079
SIOCSIFMTU: Invalid argument
However the virtual e1000 from VMWare ESX silently accept any value;
then it will mostly work, and fail in mysterious way and only with
certain protocols (such as nfs).
In the case of VMWare virtual machines, using a vmnet3 virtual network
adapter works fine with a mtu of 9000 under NFS. Therefore the problem
is solved.
For the sake of completeness and curiosity, I'll try and see what
happens with a KVM e1000 virtual device.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
next prev parent reply other threads:[~2013-09-11 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 17:18 Hard to debug NFS loss of connectivity Emmanuel Florac
2013-09-05 20:45 ` J. Bruce Fields
2013-09-05 21:34 ` Emmanuel Florac
2013-09-05 21:40 ` J. Bruce Fields
2013-09-06 15:57 ` Emmanuel Florac
2013-09-06 16:07 ` J. Bruce Fields
2013-09-06 16:55 ` Emmanuel Florac
2013-09-10 13:28 ` J. Bruce Fields
2013-09-10 13:34 ` Emmanuel Florac
2013-09-06 17:15 ` Jim Rees
2013-09-11 15:11 ` Emmanuel Florac [this message]
2013-09-11 20:14 ` Hard to debug NFS loss of connectivity: problem solved J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130911171145.323f9b9e@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).