From: Razvan Gavril <razvan.g@plutohome.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG] NFS with multiple clients connected
Date: Thu, 06 Jul 2006 18:15:58 +0300 [thread overview]
Message-ID: <44AD292E.6040100@plutohome.com> (raw)
I have a nfs server(kernel-server) which i use as a boot server for
several other machines on the network. Starting with 2.6.16 i started
noticing that when having more than one of the clients doing a lot of
in/out on their mounted nfs shares at list one of then starts to to have
problems when writing (don't know about reading) files. For example dpkg
writes strange things it the /var/lib/dpkg/status file even if it worked
perfectly before the kernel upgrade.
Every time an diskless computer fails to write corectly to the nfs
filesystem i got this messages on the nfs server (dmesg):
RPC: bad TCP reclen 0x3c390000 (large)
RPC: bad TCP reclen 0x31006261 (non-terminal)
RPC: bad TCP reclen 0x73752070 (non-terminal)
RPC: bad TCP reclen 0x52610100 (non-terminal)
Is very simple to spot this behaver (1 write-error for client / 1 rpc
message in server's dmesg) because apt-get is always giving an error
message when the /var/lib/dpkg/status file contains something that it
shouldn't. An it also can be very ease to reproduce.
I tested with 2.6.17 and got the same error, although when using 2.6.15
didn't got any errors and the clients worked perfect. Since i'm kind of
forced to use a kernel version > 2.6.15 i really, really need to solve
this bug. I would be glad to do it myself but i don't have the knowledge
to do it so if is anybody that can help i can offer all the information
that i could and also access to a system so he can track the problem.
--
Razvan Gavril
next reply other threads:[~2006-07-06 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 15:15 Razvan Gavril [this message]
2006-07-06 15:27 ` [BUG] NFS with multiple clients connected Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 16:32 Razvan Gavril
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=44AD292E.6040100@plutohome.com \
--to=razvan.g@plutohome.com \
--cc=linux-kernel@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