From: "Gabor Z. Papp" <gzp-2g/1Y3AqmNE@public.gmane.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs-utils mountd getfh failed: No such file or directory
Date: Thu, 18 Dec 2008 15:36:54 +0100 [thread overview]
Message-ID: <x67i5x4kjd@gzp> (raw)
In-Reply-To: 49498029.1080307@RedHat.com
* Steve Dickson <SteveD@redhat.com>:
| > 2008 Dec 16 15:48:44 <daemon.warning> gzp mountd[1748]: getfh failed: No such file or directory
| >
| > Found the revelant code in the mountd source, but I don't know what is this error.
| This might be due to the fact that the nfsd module is not loaded when
| mountd is started since it appears mountd is not using the new caching.
| Make sure a 'modprobe nfsd' happens before mountd is started...
Thanks, I have found the problem. The exported filesystem wasn't
mounted and the mountpoint is on 2.6 initrd. Read in the manpage
that can't be exported via nfs.
prev parent reply other threads:[~2008-12-18 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 15:38 nfs-utils mountd getfh failed: No such file or directory Gabor Z. Papp
2008-12-17 22:41 ` Steve Dickson
2008-12-18 14:36 ` Gabor Z. Papp [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=x67i5x4kjd@gzp \
--to=gzp-2g/1y3aqmne@public.gmane.org \
--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