LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Cannot mount nfs share from old Slackware on new 14.2 nfs server. (https://www.linuxquestions.org/questions/slackware-14/cannot-mount-nfs-share-from-old-slackware-on-new-14-2-nfs-server-4175601473/)

thordn 03-10-2017 11:06 AM

Cannot mount nfs share from old Slackware on new 14.2 nfs server.
 
Not finding anything relevant with Google i come here for help.

I recently updated some machines to Slackware 14.2

Problem is i have a Slackware 4.0 machine running kernel 2.2.25 and that machine cannot mount a nfs share on the 14.2 machine. However mounting it from a machine running 14.1 works fine.

/etc/exports on 14.2 machine (10.155.44.44):
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
/exp turbo(rw,no_root_squash,async,no_subtree_check)
/export 10.155.44.0/24(rw,no_root_squash,async,no_subtree_check)
/export 10.155.75.0/24(rw,no_root_squash,async,no_subtree_check)

When trying to mount i get the following:

turbo:~# mount -v -t nfs 10.155.44.44:/exp /exp
mount: wrong fs type, bad option, bad superblock on 10.155.44.44:/exp,
or too many mounted file systems

Any ideas?

Didier Spaier 03-11-2017 11:23 AM

Ideally to help you one could try to reproduce the issue.

But for that this person would need to still run a distribution released on Mon May 17 20:17:35 CDT 1999 for which support has ceased many years ago and with a 13 years old kernel... Not sure there be many people fitting the bill.

That's probably not the answer you expect, but I think it's about time to upgrade.

upnort 03-11-2017 01:47 PM

I am not an NFS guru, but some things I might check:

NFS won't run unless the rpc port mapper is running. The /etc/rc.d/rc.rpc script changed from 14.1 to 14.2. Check that the script you are running is the correct rc.d script for 14.2 and not 14.1. Also the portmap package no longer exists in 14.2.

On the NFS server check the process list (ps ax | grep rpc):

/sbin/rpcbind
/sbin/rpc.statd
/usr/sbin/rpc.rquotad
/usr/sbin/rpc.mountd

On the NFS server run showmount -e to verify the exports.

On the NFS server run netstat -an | grep :2049 to verify the NFS server port is open. Running nmap localhost also should show port 2049 open as well as port 111 (rpcbind).

On the NFS server running ps ax | grep nfsd should show at least a default of 8 counts of the NFS daemon running.

thordn 03-12-2017 05:33 PM

Quote:

Originally Posted by upnort (Post 5682132)
I am not an NFS guru, but some things I might check:

NFS won't run unless the rpc port mapper is running. The /etc/rc.d/rc.rpc script changed from 14.1 to 14.2. Check that the script you are running is the correct rc.d script for 14.2 and not 14.1. Also the portmap package no longer exists in 14.2.

On the NFS server check the process list (ps ax | grep rpc):

/sbin/rpcbind
/sbin/rpc.statd
/usr/sbin/rpc.rquotad
/usr/sbin/rpc.mountd

On the NFS server run showmount -e to verify the exports.

On the NFS server run netstat -an | grep :2049 to verify the NFS server port is open. Running nmap localhost also should show port 2049 open as well as port 111 (rpcbind).

On the NFS server running ps ax | grep nfsd should show at least a default of 8 counts of the NFS daemon running.

Everything above looks OK.

I did some more digging and it seems the mount command sends some info that the new portmapper does not like. I found out that for slackware 8 mount worked, so i took the slack 8.1 version of mount and built it on slack 4 and that seems to do the trick.

upnort 03-12-2017 06:32 PM

Quote:

so i took the slack 8.1 version of mount and built it on slack 4 and that seems to do the trick
Got to love quilt work solutions. Been there, done that. :)

I am guessing the original problem is related to using NFSv2.


All times are GMT -5. The time now is 07:13 PM.