On Wed, 2007-08-15 at 19:38 -0700, Anoop Rajendra wrote:
> Hi. I'm having trouble accessing a shared directory over NFSv4 on a
> CentOS 4.5 machine.
>
> My export file reads
>
> /test 10.0.0.0/255.0.0.0(ro,async,insecure,nohide,no_subtree_check)
>
> I've also tried to include the fsid=0 argument in my /etc/exports
> file. That gives me a whole different error
fsid MUST be included on the main mount point like this:
/export
gss/krb5(fsid=0,sync,no_root_squash,insecure,no_subtree_check,anonuid=65534,anongid=65534)
/export/home1
gss/krb5(rw,nohide,sync,insecure,no_subtree_check,anonuid=65534,anongid=65534)
/export/home2
gss/krb5(rw,nohide,sync,insecure,no_subtree_check,anonuid=65534,anongid=65534)
#
# legacy mounts
# /export/home1
192.168.159.1/24(rw,sync,no_root_squash,insecure,no_subtree_check)
# /export/home2
192.168.159.1/24(rw,sync,no_root_squash,insecure,no_subtree_check)
(sorry, evolution forces extra linebreaks, after the pathnames),
so /eports is the base path, home1 and home2 the exported filesystems. I
use kerberos so I do not have the hostnames there, but the gss/krb5
>
> [root@pebble-anoop ~]# mount -v -t nfs4 pebble-anoop:/test/ /mnt/
> mount: pinging: prog 100003 vers 4 prot tcp port 2049
> mount: special device pebble-anoop:/test/ does not exist
>
Here is your real problem: nfs mount points are relative to the base
export point, i.e. /export in my case. If you only have /test exported,
you have to mount peobble-anop:/ not ../test!
In my case I mount server:/home1 and server:/home2
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
