LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-10-2017, 11:06 AM   #1
thordn
LQ Newbie
 
Registered: Mar 2017
Location: Tyresö, Sweden
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
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?
 
Old 03-11-2017, 11:23 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,164

Rep: Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272Reputation: 2272
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.

Last edited by Didier Spaier; 03-11-2017 at 11:27 AM.
 
Old 03-11-2017, 01:47 PM   #3
upnort
Member
 
Registered: Oct 2014
Distribution: Slackware, CentOS
Posts: 202

Rep: Reputation: Disabled
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.
 
Old 03-12-2017, 05:33 PM   #4
thordn
LQ Newbie
 
Registered: Mar 2017
Location: Tyresö, Sweden
Distribution: Slackware
Posts: 5

Original Poster
Rep: Reputation: Disabled
Talking

Quote:
Originally Posted by upnort View Post
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.
 
Old 03-12-2017, 06:32 PM   #5
upnort
Member
 
Registered: Oct 2014
Distribution: Slackware, CentOS
Posts: 202

Rep: Reputation: Disabled
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 14.1 server + client : can't mount NFS share kikinovak Slackware 5 05-03-2014 07:06 AM
[SOLVED] NFS Client Unable to Mount the NFS Share devUnix Linux - Server 7 10-31-2013 01:12 PM
[SOLVED] NFS mount fails (times out): NFS server is in DMZ, NFS client is in intranet Hiroshi Linux - Networking 2 05-24-2010 10:22 AM
mount.nfs: mount to NFS server 'jesse' failed: timed out, retrying keupie Linux - Networking 3 06-05-2009 07:03 PM
Unable to mount NFS share present on server to client vathsan AIX 1 11-10-2008 11:19 PM


All times are GMT -5. The time now is 12:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration