From: Razvan Gavril <razvan.g@plutohome.com>
To: Chuck Lever <chucklever@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Bug starting 2.6.16 - rpc: bad TCP reclen
Date: Wed, 19 Jul 2006 18:52:24 +0300 [thread overview]
Message-ID: <44BE5538.4080508@plutohome.com> (raw)
In-Reply-To: <76bd70e30607190822o1b76b04w906729300160f7d0@mail.gmail.com>
Chuck Lever wrote:
> I haven't seen other reports like this recently. It could be a
> hardware problem on your server or in your network (like a bad server
> NIC). A network trace would be the way to start tracking this down.
>
> sudo tcpdump -s0 -w /tmp/dump
>
> on your server. Stop the dump when the server starts reporting the
> TCP stream problems. Then take a look at the end of the dump with
> tethereal.
>
A hardware problem is almost impossible since we test it on a lot of
different computers. I'm really interested if someone can explain what
that message is meaning, it doesn't make much sense to me cause i don't
know anything about rpc.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-07-19 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 11:36 Buf starting 2.6.16 - rpc: bad TCP reclen Razvan Gavril
2006-07-19 14:46 ` Bug " Razvan Gavril
2006-07-19 15:22 ` Chuck Lever
2006-07-19 15:52 ` Razvan Gavril [this message]
2006-07-20 4:29 ` Neil Brown
2006-07-20 8:38 ` Bernd Schubert
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=44BE5538.4080508@plutohome.com \
--to=razvan.g@plutohome.com \
--cc=chucklever@gmail.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.