From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs server issues
Date: Thu, 01 Dec 2011 10:59:51 -0600 [thread overview]
Message-ID: <4ED7B287.4010802@gmail.com> (raw)
In-Reply-To: <4ED77E8E.2040304@RedHat.com>
Steve Dickson wrote:
>
> On 11/30/2011 06:31 PM, Bruce Dubbs wrote:
>> I am trying to document the installation of nfs for Linux From
>> Scratch. The client works, but the server does not and I'm looking
>> for some help. If this is the wrong place to ask for help, please
>> redirect me.
>> For now, I am only trying to get nfs version 3 to work.
>>
>> # mount -t nfs -o nfsvers=3 lfs6:/home/bdubbs /mnt/test
>> [ mounts OK ]
>> # mount -t nfs -o nfsvers=3 localhost:/usr/src /mnt/tmp
>> # mount.nfs: requested NFS version or transport protocol is not supported
> The reason you getting the mounting error to localhost is because there are
> no NFS services registered with rpcbind. Note the lack of nfs entires in
> your rpcinfo -p output. For the above mount to work you would need at least
> the following entry:
> 100003 3 tcp 2049 nfs
> Figure out why that is not happening and you find the problem...
Yes, I thought that might be the problem. The hard part is figuring out
why. I am running 'rpc.nfsd -p 2049 8' and I would think that would do
it, but it's not registering with rpcbind. The actual nfsd daemon is
running in the kernel.
I looked at the nfsd.c source and nfsdfs is mounted in /proc correctly.
The threads seem to be started properly in nfssvc_threads() and there
are no error messages either on the terminal or in syslog.
I'm just not familiar enough with the code to see where nfs is supposed
to register with rpcbind. That's where I'm trying to get help. I
suspect I've done something wrong with the build or configuration, but I
don't see where. Is the kernel nfsd process supposed to register when
it starts?
One other thing. When I try to mount the share from a remote (older)
system, the error message is sightly different: "RPC Error: Program not
registered", but I think that means the same thing as above.
-- Bruce
next prev parent reply other threads:[~2011-12-01 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 23:31 nfs server issues Bruce Dubbs
2011-12-01 2:43 ` Jim Rees
[not found] ` <4ED704E5.2030500@gmail.com>
2011-12-01 5:07 ` Bruce Dubbs
2011-12-01 13:18 ` Steve Dickson
2011-12-01 16:59 ` Bruce Dubbs [this message]
2011-12-01 17:25 ` Bruce Dubbs
2011-12-01 13:19 ` peter.staubach
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=4ED7B287.4010802@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@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