From: Arnaud Giersch <arnaud.giersch@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: "svc: unknown version (3)" when CONFIG_NFSD_V4=y
Date: Wed, 10 Jan 2007 15:15:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20070110T155948-40@post.gmane.org> (raw)
In-Reply-To: <368438638.13038@ustc.edu.cn>
Fengguang Wu <fengguang.wu <at> gmail.com> writes:
> root ~# mount localhost:/suse /mnt
> [ 132.678204] svc: unknown version (3 for prog 100227, nfsd)
>
> I've confirmed that 2.6.20-rc2-mm1, 2.6.20-rc3-mm1, 2.6.19-rc6-mm1 all
> have this warning, while 2.6.17-2-amd64 is good.
I get the same log messages here with 2.6.19. I also noticed the following
messages when starting rpc.nfsd:
nfsd[1287]: nfssvc: writting fds to kernel failed: errno 0 (Success)
nfsd[1287]: nfssvc: writting fds to kernel failed: errno 0 (Success)
These messages appeared with kernel 2.6.19 too. I however don't know if
this could be related to the other messages.
I use nfs-utils 1.0.10 on Debian Etch.
Arnaud Giersch
next prev parent reply other threads:[~2007-01-10 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070105024226.GA6076@mail.ustc.edu.cn>
2007-01-05 2:42 ` Fengguang Wu
2007-01-05 12:25 ` Trond Myklebust
[not found] ` <20070105124822.GA7901@mail.ustc.edu.cn>
2007-01-05 12:48 ` Fengguang Wu
2007-01-10 6:01 ` Neil Brown
[not found] ` <20070110141756.GA5572@mail.ustc.edu.cn>
2007-01-10 14:17 ` Fengguang Wu
2007-01-10 15:15 ` Arnaud Giersch [this message]
2007-01-11 3:59 ` Neil Brown
[not found] ` <20070111145309.GA6226@mail.ustc.edu.cn>
2007-01-11 14:53 ` Fengguang Wu
2007-01-11 22:04 ` Neil Brown
[not found] ` <20070112023251.GA6136@mail.ustc.edu.cn>
2007-01-12 2:32 ` Fengguang Wu
2007-01-12 19:43 ` Neil Brown
[not found] ` <20070113021320.GA6055@mail.ustc.edu.cn>
2007-01-13 2:13 ` Fengguang Wu
2007-01-14 22:32 ` Neil Brown
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=loom.20070110T155948-40@post.gmane.org \
--to=arnaud.giersch@free.fr \
--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