From: Jeff Layton <jlayton@poochiereds.net>
To: cl@qgenuity.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: Setting up NFS on Centos 6.6
Date: Sat, 15 Nov 2014 19:21:53 -0500 [thread overview]
Message-ID: <20141115192153.0ec58d54@synchrony.poochiereds.net> (raw)
In-Reply-To: <e7097d3e747a2a1e46c37d88cea3c8a2.squirrel@www.qgenuity.com>
On Sun, 16 Nov 2014 00:07:23 +0900
cl@qgenuity.com wrote:
> Hello,
>
> I'm having an unusual amount of trouble setting up Centos 6.6 as an NFS
> server. I have already created my exportfs file and run "chkconfig nfs
> on".
>
> My copy of centos is running inside a virtual bubble. The server provider
> has loaded the nfsd module.
>
> I run:
> chkconfig nfs on
> service rpcbind start
> service nfs start
>
> The final command produces:
> # service nfs start
> FATAL: Module nfsd not found.
> FATAL: Error running install command for nfsd
> Starting NFS services: [ OK ]
> Starting NFS quotas: [ OK ]
> Starting NFS mountd: [ OK ]
> Starting NFS daemon: [ OK ]
> Starting RPC idmapd: [ OK ]
>
> (I've been following the guide found here:
> http://openvz.org/NFS_server_inside_container which says that "module nfsd
> not found" is no problem.)
>
> showmount -e produces:
> Export list for (server):
> /(directory) (address)
>
> but when I try to mount
> mount -t nfs -v (address):/(dir) /mnt/nfs
> mount.nfs: timeout set for (date)
> mount.nfs: trying text-based options 'vers=4,addr=::1,clientaddr=::1'
> mount.nfs: mount(2): No such device
> mount.nfs: No such device
>
>
> Does anyone know what I need to do to get nfs working?
>
-ENODEV is what you usually get when you can't plug in nfs.ko. Perhaps
your server provider needs to plug that in as well?
--
Jeff Layton <jlayton@poochiereds.net>
prev parent reply other threads:[~2014-11-16 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 15:07 Setting up NFS on Centos 6.6 cl
2014-11-16 0:21 ` Jeff Layton [this message]
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=20141115192153.0ec58d54@synchrony.poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=cl@qgenuity.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