From: "Gabor Z. Papp" <gzp-2g/1Y3AqmNE@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: nfs-utils mountd getfh failed: No such file or directory
Date: Tue, 16 Dec 2008 16:38:14 +0100 [thread overview]
Message-ID: <x6k5a0166x@gzp> (raw)
Hello,
I would like to use nfs-utils 1.1.4 (and 1.1.*) in the following environment:
[kernel]
Linux gzp 2.6.27.9-gzp2 #1 Tue Dec 16 15:17:04 CET 2008 i686 GNU/Linux
[glibc]
GNU C Library stable release version 2.3.6, by Roland McGrath et al.
Compiled by GNU CC version 4.1.2.
Compiled on a Linux 2.4.34-gzp1 system on 2007-04-04.
But getting this error after trying to mount from remote:
2008 Dec 16 15:48:44 <daemon.info> gzp portmap[1843]: connect from 192.168.1.1 to getport(nfs)
2008 Dec 16 15:48:44 <daemon.info> gzp portmap[1844]: connect from 192.168.1.1 to getport(mountd)
2008 Dec 16 15:48:44 <daemon.notice> gzp mountd[1748]: authenticated mount request from 192.168.1.1:835 for /var/archive/sda1 (/var/archive/sda1)
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.
next reply other threads:[~2008-12-16 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 15:38 Gabor Z. Papp [this message]
2008-12-17 22:41 ` nfs-utils mountd getfh failed: No such file or directory Steve Dickson
2008-12-18 14:36 ` Gabor Z. Papp
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=x6k5a0166x@gzp \
--to=gzp-2g/1y3aqmne@public.gmane.org \
--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