From: Shehjar Tikoo <shehjart-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Missing xtab entry after nfsd startup
Date: Wed, 24 Jun 2009 13:59:51 +0530 [thread overview]
Message-ID: <4A41E3FF.4060303@gluster.com> (raw)
Hi All
I am running into a "Permission denied" at the client when I try to
do a mount of an exported directory.
Looking at the HOWTO, I see that there seems to be some inconsistency
as the entries for the export are missing from the /var/lib/nfs/xtab.
For eg:
On the Server:
[root@192 shehjart]# cat /etc/exports
/data/shehjart/volumes/disk1 *(rw,no_root_squash)
[root@192 shehjart]# /etc/init.d/nfs start
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
[root@192 shehjart]# cat /proc/fs/nfs/exports
# Version 1.1
# Path Client(Flags) # IPs
[root@192 shehjart]# cat /var/lib/nfs/xtab
[root@192 shehjart]#
On the client, after the above commands:
root@indus:~# mount 192.168.1.201:/data/shehjart/volumes/disk1 /mnt/
mount.nfs: 192.168.1.201:/data/shehjart/volumes/disk1 failed, reason
given by server: Permission denied
After this failed mount, the server says:
[root@192 shehjart]# cat /proc/fs/nfs/exports
# Version 1.1
# Path Client(Flags) # IPs
/data/shehjart/volumes/disk1
*(rw,no_root_squash,sync,wdelay,no_subtree_check)
[root@192 shehjart]# cat /var/lib/nfs/xtab
[root@192 shehjart]#
even with:
[root@192 shehjart]# exportfs -ra
[root@192 shehjart]# cat /var/lib/nfs/xtab
[root@192 shehjart]#
And the "Permission denied" persists.
tshark shows that the MNT request fails because the
server returns a MNT3ERR_ACCES.
Server is:
[root@192 shehjart]# uname -a
Linux n1 2.6.18-128.1.10.el5xen #1 SMP Thu May 7 11:07:18 EDT 2009
x86_64 x86_64 x86_64 GNU/Linux
Client is a debian testing:
Linux indus 2.6.18-5-amd64 #1 SMP Thu May 31 23:51:05 UTC 2007 x86_64
GNU/Linux
Thanks
Shehjar
reply other threads:[~2009-06-24 8:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A41E3FF.4060303@gluster.com \
--to=shehjart-+fkpdpinhgjbdgjk7y7tuq@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