From: Voluspa <lista1@comhem.se>
To: linux-kernel@vger.kernel.org
Subject: NFS regression since 2.6.0-test3 (in -test4 and 4-mm1)
Date: Wed, 27 Aug 2003 05:25:17 +0200 [thread overview]
Message-ID: <20030827052517.79d65038.lista1@comhem.se> (raw)
Transfer time doubled and kernel log is swelling...
Remote is exported rw,no_root_squash and runs a Slackware 7.1.0
(Universal NFS Server 2.2beta47) kernel 2.2.16. Mounted here with a
simple "-t nfs". Both remote and local is ext2.
_2.6.0-test3_
"cp -a" the remote /etc directory takes 2 minutes. /var/log/kernel says:
Aug 27 03:59:59 loke kernel: eth0: media is TP.
Aug 27 04:02:34 loke kernel: nfs warning: mount version older than
kernel
Duh! I'm using your util-linux-2.12pre.tar.gz so stop complaining.
_2.6.0-test4 and -mm1_
The transfer takes 4 minutes and log is filled with:
Aug 27 04:20:47 loke kernel: eth0: media is TP.
Aug 27 04:22:34 loke kernel: nfs warning: mount version older than
kernel
Aug 27 04:23:21 loke kernel: nfs: server oden.fish.net not
responding, still trying
Aug 27 04:23:41 loke kernel: nfs: server oden.fish.net OK
Aug 27 04:24:00 loke kernel: nfs: server oden.fish.net not responding,
still trying
[Lots of lines deleted]
Aug 27 04:27:00 loke kernel: nfs: server oden.fish.net OK
Aug 27 04:27:01 loke kernel: nfs: server oden.fish.net not responding,
still trying
Aug 27 04:27:01 loke kernel: nfs: server oden.fish.net OK
Last night the complete backup took 9 hours (transfer of 1.2 gig).
That's why I noticed the issue.
Mvh
Mats Johannesson
next reply other threads:[~2003-08-27 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 3:25 Voluspa [this message]
2003-08-27 7:10 ` Frank Cusack
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=20030827052517.79d65038.lista1@comhem.se \
--to=lista1@comhem.se \
--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
Powered by JetHome