From: dap <dap@kenyer.hu>
To: linux-kernel@vger.kernel.org
Subject: weird NFSv3 getaddr storm when fileserver upgraded to 2.6
Date: Sun, 07 Nov 2004 16:31:05 +0100 [thread overview]
Message-ID: <1099841465.28539.152.camel@localhost> (raw)
I've upgraded my NFS server from 2.4.25 to 2.6.9 at friday night and
the 2.4.x clients started to flood it with getaddr requests:
http://innocence.nightwish.hu/dap/getaddrstat/rpcga.html
clients are 2.4.x boxes with increased 'ac' values:
10_1_1_1:~# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / nfs rw,v3,rsize=4096,wsize=4096,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,udp,nocto,nolock,addr=10.1.1.251 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
10.1.1.251:/mnt/htdocs /http nfs rw,v3,rsize=32768,wsize=32768,acregmin=120,acregmax=120,acdirmin=120,acdirmax=180,hard,udp,nocto,lock,addr=10.1.1.251 0 0
there's no getattr flood for some time if I reboot the clients (like
saturday night), but it begins again at a point and only the reboot can
calm it down for a while. 2.4.25 worked fine for months.
--
dap
reply other threads:[~2004-11-07 15:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1099841465.28539.152.camel@localhost \
--to=dap@kenyer.hu \
--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 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.