NFS issues

phoenixcomm · 06-07-2015, 09:08 PM

ok Im stumped...
I have network of Linux only boxes
1. Server and my desktop
2. Client and my desktop on my workbench
3 - 4 media streamers (not part of this discussion).

Code:

part of my fstab:
/dev/sdc1 /mnt/MyData/ auto nosuid,nodev,nofail 0 0
/dev/sdb2 /mnt/MyMedia auto nosuid,nodev,nofail,x-gvfs-show 0 0

Code:

now my exports:
/mnt/MyMedia/Music	192.168.1.1/24(ro,async,no_root_squash,subtree_check)
/mnt/MyMedia/media	192.168.1.1/24(ro,async,no_root_squash,subtree_check)
/mnt/MyMedia/p2p	192.168.1.1/24(rw,async,no_root_squash,subtree_check)
/mnt/MyData/public	192.168.1.1/24(rw,async,no_root_squash,subtree_check)

I have NFS v4 installed on my server and it is working:

Code:

showmount -e: 
Export list for Server:
/mnt/MyData/public 192.168.1.1/24
/mnt/MyMedia/p2p   192.168.1.1/24
/mnt/MyMedia/media 192.168.1.1/24
/mnt/MyMedia/Music 192.168.1.1/24

all should be good..

and both hosts files have been updated

but now my #2 desktop wont boot as I am geting this error:
mount.nfs remote share not in host:dir format....

I have googled this but it shows a Linux/Windows network

Anybody have any answers
Cris.

ferrari · 06-07-2015, 10:43 PM

Can you show us how you are mounting on the client?

For example, a casual mount might look like

Code:

mount -t nfs -o options host:/remote/export /local/directory

and for mounting via /etc/fstab

Code:

host:/path/to/export /local_mountpoint nfs <options> 0 0

phoenixcomm · 06-08-2015, 12:46 AM

the mount on the client was done in fstab:

Code:

$vi /etc/fstab
Whirlwind:/mnt/MyData/public  /mnt/public
whirlwind:/mnt/MyMedia/Music /mnt/music

ferrari · 06-08-2015, 01:36 AM

I'm wondering if your client needs to specify nfs4 explicitly?

Code:

Whirlwind:/mnt/MyData/public /mnt/public nsf4

suicidaleggroll · 06-08-2015, 11:13 AM

One of your hosts is upper case, the other is lower. Which one is it? What do you have in /etc/hosts?

phoenixcomm · 06-08-2015, 11:24 AM

Quote:

Originally Posted by suicidaleggroll

One of your hosts is upper case, the other is lower. Which one is it? What do you have in /etc/hosts?

It really doesn't mater.

RFC1035 sec 2.3.1 <http://www.ietf.org/rfc/rfc1035.txt>

"Note that while upper and lower case letters are allowed in domain
names, no significance is attached to the case. That is, two names with
the same spelling but different case are to be treated as if identical."

Cris H.

ferrari · 06-08-2015, 03:11 PM

Yes, but the request about /etc/hosts could be valid (if there is no domain name server in use). Does 'Whirlwind' resolve to an IP address? (Can you ping Whirlwind?)

joec@home · 06-08-2015, 03:15 PM

Quote:

Originally Posted by phoenixcomm

It really doesn't mater.

RFC1035 sec 2.3.1 <http://www.ietf.org/rfc/rfc1035.txt>

"Note that while upper and lower case letters are allowed in domain
names, no significance is attached to the case. That is, two names with
the same spelling but different case are to be treated as if identical."

Cris H.

To quote Pirates of the Caribbean, "The code is what you call guidelines than actual rules." Linux tends to be picky about case sensitivity for hostnames. Not totally certain on this specific issue, but I have seen this cause many a problem in others.

phoenixcomm · 06-09-2015, 06:54 AM

Quote:

Originally Posted by ferrari

Yes, but the request about /etc/hosts could be valid (if there is no domain name server in use). Does 'Whirlwind' resolve to an IP address? (Can you ping Whirlwind?)

as you can see upper and lower cases works fine.... ie But this is a Red Herring. LOL

Code:

harrison@Whirlwind /mnt/MyData/home/harrison $ ping whirlwind
PING Whirlwind (127.0.1.1) 56(84) bytes of data.
64 bytes from Whirlwind (127.0.1.1): icmp_seq=1 ttl=64 time=0.016 ms
64 bytes from Whirlwind (127.0.1.1): icmp_seq=2 ttl=64 time=0.048 ms
64 bytes from Whirlwind (127.0.1.1): icmp_seq=3 ttl=64 time=0.046 ms
^C
--- Whirlwind ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.016/0.036/0.048/0.016 ms
harrison@Whirlwind /mnt/MyData/home/harrison $ ping Whirlwind
PING Whirlwind (127.0.1.1) 56(84) bytes of data.
64 bytes from Whirlwind (127.0.1.1): icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from Whirlwind (127.0.1.1): icmp_seq=2 ttl=64 time=0.043 ms
64 bytes from Whirlwind (127.0.1.1): icmp_seq=3 ttl=64 time=0.042 ms
^C
--- Whirlwind ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.036/0.040/0.043/0.006 ms
harrison@Whirlwind /mnt/MyData/home/harrison $

ferrari · 06-09-2015, 01:53 PM

Did you try my suggestion (post #4) regarding 'nsf4'?

suicidaleggroll · 06-09-2015, 01:57 PM

Can you ping whirlwind/Whirlwind from the guest machine? Your above output is just pinging localhost.

Can you mount the NFS share manually?

Also you have no options on your mount, eg nfs version or _netdev.

phoenixcomm · 06-09-2015, 09:08 PM

Quote:

Originally Posted by ferrari

Did you try my suggestion (post #4) regarding 'nsf4'?

No. I had a bad few days... no worries I have to lay down a new OS as the client is locked up and does not make the boot...

Most likely will get to it tomorrow

Cris

phoenixcomm · 06-09-2015, 09:12 PM

Quote:

Originally Posted by suicidaleggroll

Can you ping whirlwind/Whirlwind from the guest machine? Your above output is just pinging localhost.
Can you mount the NFS share manually?
Also you have no options on your mount, eg nfs version or _netdev.

Most likely but, as the client is not making the boot, pining it is moot.
Yes I have mounted the client with that same string... before I put it into fstab.

What I might end up doing is the great cheat...
creating a shell script that dose the mount after I have booted and loged on...

Cris

mralk3 · 06-09-2015, 09:52 PM

Quote:

Originally Posted by phoenixcomm

No. I had a bad few days... no worries I have to lay down a new OS as the client is locked up and does not make the boot...

Most likely will get to it tomorrow

Cris

No reason to reinstall. Get a live cd and boot up the system. Then mount the hard drive and edit the /etc/fstab. Reboot the system and see if it will start up... It doesn't even matter what live cd you use, as long as it has the ability to read the file system on the unbootable disk.

EDIT
Your problem is likely just that you have not formatted your fstab with the proper options following the device and mount point.

phoenixcomm · 06-12-2015, 04:58 PM

Quote:

Originally Posted by mralk3

Always remember to RTFM before posting.
Not sure about what question to ask, where to ask, or how to ask? Read ALL of this!

#1 I really did both... I find this to be highly offensive.
#2 even though your comment about just using a live CD was a good tempory solution. To get the system back up.
#3 BTW most of the notes on NFS concern type 3 which uses automounter, which type 4 doesn't use.
#4 I beleave that I barfed on the clients mount options not the mounting point.
#5 I will have to wait till Saturday to do anything.
#6 Oh WT_!
enjoy
Cris.
https://www.linuxcounter.net/user/587516