On Wed, Nov 18, 2009 at 5:18 PM, Joshua Baker-LePain <jlb17 at duke.edu> wrote: > On Wed, 18 Nov 2009 at 4:05pm, Tim Nelson wrote > >> ----- "Joshua Baker-LePain" <jlb17 at duke.edu> wrote: > >>> /export $CLIENT(ro,fsid=0) >>> /export/qb3 $CLIENT(rw,nohide) > >> Your export: >> >> /export/qb3 $CLIENT(rw,nohide) >> >> And your mount: >> >> mount -t nfs4 $SERVER:/qb3 /usr/local/sge62/qb3 >> >> The remote path is wrong. Either that's a typo or could be the cause of >> your problem? > > No, that's how NFSv4 mounts work -- it's relative to the pseudo-root (the > fsid=0 entry) on the server. And the mount succeeds. But it's a > read-only mount, where it should be rw. > Not sure if this applies in your FS4 setup, but most of my NFS permissions errors have stemmed from user ID mismatches on the host server. My NFS4 mounts are not using any true NFS4 features, however.