From: Voluspa <lista2@comhem.se>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS on 2.6.0-test9:
Date: Mon, 3 Nov 2003 16:34:55 +0100 [thread overview]
Message-ID: <20031103163455.57d24178.lista2@comhem.se> (raw)
On 2003-11-03 13:42:35 Luke Driscoll wrote:
>On a kernel 2.6.0-test9 as an NFS client I am having trouble
>transferring data to and from NFS servers. It it extraordinarily
>slow. I receive the following information in dmesg:
>
>nfs warning: mount version older than kernel
>nfs: server safe not responding, still trying
You and me the same. Here's a message I sent to
nfs@lists.sourceforge.net this Friday:
--quote--
xSubject: 2.6.0-test3-bk10-final regression getting out of hand
xDate: Fri, 31 Oct 2003 21:48:51 +0100
As reported in:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106195494828814&w=2
I'm experiencing a serious NFS regression since 2.6.0-test3-bk10-final
(bk-set determined now). Since that, along the road to 2.6.0-test9,
something has gotten completely out of hand.
cp -a /mnt/oden/etc .
_2.6.0-test3-bk10_
2 minutes
_2.6.0-test3-bk10-final_
3 minutes 47 seconds
_2.6.0-test9_
29 minutes 54 seconds
Nothing has changed in hardware or setup, and the cp tests were done
today. Not being a programmer I tried to delete individual patches in
the bk-set, but couldn't find the exact breakage point.
Erasing changes to:
linux-2.6.0-test3-bk10/fs/nfs/dir.c
No change.
Erasing changes to:
linux-2.6.0-test3-bk10/fs/nfs/nfsroot.c
No change.
Erasing changes to:
linux-2.6.0-test3-bk10/include/linux/sunrpc/timer.h
linux-2.6.0-test3-bk10/net/sunrpc/timer.c
No change.
Erasing changes to:
linux-2.6.0-test3-bk10/net/sunrpc/clnt.c
Doesn't compile.
Erasing changes to:
linux-2.6.0-test3-bk10/include/linux/sunrpc/xprt.h
linux-2.6.0-test3-bk10/net/sunrpc/xprt.c
Doesn't compile.
Using TCP or DIRECTIO in -test9 makes no difference. Here's the
relevant .config-section:
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_GSS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
--unquote--
Mvh
Mats Johannesson
next reply other threads:[~2003-11-03 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 15:34 Voluspa [this message]
2003-11-03 16:09 ` NFS on 2.6.0-test9: Trond Myklebust
2003-11-03 17:13 ` Voluspa
2003-11-09 21:23 ` Voluspa
2003-11-09 22:04 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2003-11-10 7:06 Voluspa
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=20031103163455.57d24178.lista2@comhem.se \
--to=lista2@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 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.