Hi Adam,
With your help I was able to eliminate RPC error. The key is nfsvers=2
as reported many other people using user space nfs also.
With some more googleing Now I was able to increase debug level.
on client side:
rpcdebug -m nfs -s all # set debug level ; check dmesg
showmount -e 192.168.178.30
mount -o nfsvers=2,ro 192.168.178.30:/mnt/sda1 /mnt/snfs
Unfortunately mount not yet working.
Now I had another issue:
[ 632.625651] NFS: nfs mount opts='nfsvers=2,addr=192.168.178.30'
[ 632.625660] NFS: parsing nfs mount option 'nfsvers=2'
[ 632.625669] NFS: parsing nfs mount option 'addr=192.168.178.30'
[ 632.625680] NFS: MNTPATH: '/mnt/sda1'
[ 632.625683] NFS: sending MNT request for 192.168.178.30:/mnt/sda1
[ 632.636527] NFS: MNT request succeeded
[ 632.636546] --> nfs_init_server()
[ 632.636550] --> nfs_get_client(192.168.178.30,v2)
[ 632.636556] --> nfs_get_client() = f1cf9a00 [new]
[ 632.644078] <-- nfs_init_server() = 0 [new f1cf9a00]
[ 632.644082] --> nfs_probe_fsinfo()
[ 632.644085] NFS call fsinfo
[ 632.646566] NFS reply fsinfo: -116
[ 632.646569] nfs_probe_fsinfo: error = 116
[ 632.646572] --> nfs_free_server()
[ 632.646598] --> nfs_put_client({1})
[ 632.646602] --> nfs_free_client(2)
[ 632.646637] <-- nfs_free_client()
[ 632.646650] <-- nfs_free_server()
where -nfs_probe_fsinfo: error = 116 - means a strange error. didn't
find any reason yet.
Next step will be some read only flag, maybe right problem?
Regards,
Robert