Following up on this. I looked into the /var/log/messages/ and /var/log/daemon. Both are quite after starting the portmap, mountd, and nfsd services.
Here is verbose output from the client side when mounting the share: ``` [adming@cluster-node2]~% sudo mount -t nfs -o rw,noauto -v 192.168.0.122:/nfs/testdir /home/adming/mntpt2 mount.nfs: timeout set for Thu Feb 9 11:34:52 2023 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.122,clientaddr=192.168.0.187' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.122,clientaddr=192.168.0.187' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,addr=192.168.0.122,clientaddr=192.168.0.187' mount.nfs: mount(2): Protocol not supported Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: trying text-based options 'addr=192.168.0.122' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.0.122 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.0.122 prog 100005 vers 3 prot UDP port 724 [adming@cluster-node2]~% cd mntpt2 [adming@cluster-node2]~/mntpt2% ls alfpha testfile [adming@cluster-node2]~/mntpt2% touch y touch: cannot touch 'y': Permission denied ``` Am out of ideas as what to test/debug. On Wed, Feb 8, 2023 at 9:27 PM Sandeep Gupta <[email protected]> wrote: > I have a default installation of openbsd, with portmap, mountd, nfsd > services started via rcctl. I have following entry in /etc/exports > > /nfs/testdir -alldirs -maproot=root -network=192.168.0 -mask=255.255.255.0 > > I am able to mount the exported share on client (centos) as follows: > > sudo mount -t nfs -o rw,noauto -v 192.168.0.122:/nfs/testdir mntpt3 > > From the client, I can read the contents. But writing inside the mounted > directory yields permission denied error. Looking at the docs I am not able > to find any otherconfig options for access control on the client side. > There is nothing in the logs on the server side as well. Any pointers to > debug/fix would be of great help. >
