On 11-Sep-2000 Dan Horth spoke something to the effect:
> Hiya - still having post upgrade problems - I had an NFS server 
> running on a host - worked fine prior to the upgrade but now I get 
> weird errors... ps. note names have been changed to protect the 
> innocent! :)
> 
> this is what the /etc/exports on my server looks like:
> 
> [[EMAIL PROTECTED] /root]# cat /etc/exports
> /usr 192.168.2.2 (rw)
> /usr/local/src/updates 192.168.2.2 (ro,no_root_squash)
> /mnt/cdrom 192.168.2.2 (ro,no_root_squash)
> 
> 
> 
> when I try to set up exports:
> 
> [[EMAIL PROTECTED] /root]# exportfs -ar
> 192.168.2.2:/usr: Invalid argument
> 192.168.2.2:/: Invalid argument
> 
> 
> 
> but exportfs reports the mounts are being exported:
> 
> [[EMAIL PROTECTED] /root]# exportfs -v
> /usr/local/src/updates
>                  192.168.2.2 (ro,async,wdelay,no_root_squash)
> /mnt/cdrom      192.168.2.2 (ro,async,wdelay,no_root_squash)
> /usr            192.168.2.2 (rw,async,wdelay,root_squash)
> /               192.168.2.2 (rw,async,wdelay,root_squash)

At this point and the last few bits shown, you either messed something up
in the transpositions, or it's obvious what the mistake is. Under the line
above:

        when I try to set up exports:
        [[EMAIL PROTECTED] /root].......

you show that you are located on 192.168.2.1 and trying to export from
192.168.2.2, which won't work. If thta's what you have in the exports file
on 192.168.2.1 the problem is solved by fixing that conflict.

> on the client I have this entry in /etc/fstab:
> 
> [[EMAIL PROTECTED] /root]# cat /etc/fstab
> 192.168.2.1:/usr  /serverusr  nfs  exec,dev,suid,ro,noauto,bg,soft 1 1

On mine I use something like:

192.168.0.4:/  /server nfs noauto,rw,rsize=8192,wsize=8192,timeo=14,intr

That works fine for everything. I also put "0 0" on the ends, since I don't
want fstab to signal that those partitions should be fsck'd by the wrong
system.

> and when I try to mount the /usr directory on the client I get:
> 
> [[EMAIL PROTECTED] /root]# mount /serverusr/
> mount: 192.168.2.1:/usr failed, reason given by server: Permission denied

If what I pointed out is true, this would be the expected result because
192.168.2.1 never tried to export its own /usr directory in the first
place. And it isn't allowed to export the directory for another system.

> and I get this in the log files on the server:
> 
> Sep 11 11:37:55 192.168.2.1 rpc.mountd: authenticated mount request 
> from 192.168.2.2:673 for /usr (/usr)
> Sep 11 11:37:55 192.168.2.1 rpc.mountd: getfh failed: Operation not
> permitted

True, this would also be expected.

> but I can mount /mnt/cdrom on the client just fine...

This would not. I'd like to see the whole fstab for this. This couldn't
work if the cd drive is actually mounted on the other computer.

I just tried what you have shown above. It fails every time (as I already
knew it should).

> uhm... I'm confused because this setup worked fine for me prior to 
> 6.2 upgrade. I can't be 100% this is the exact config I was using as 
> I have gone through all sorts of permutations of /etc/fstab and 
> /etc/exports trying to work out what the problem is... it's weird 
> that certain exports work ok and others don't.

Either this never worked, you mistyped the above repeatedly, or you copied
the exports file from 192.168.2.2 and didn't change addressing in the file.

If it's mistyped, I had a similar problem untill I changed a few
permissions, rebooted, restarted nfs and nfslock, all several times. I have
no idea what fixed it. Tweaking didn't because I never changed anything.

-- 
Excuse my english. I went to US public school.



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to