Help needed with NFS
Posted: Wed Dec 01, 2010 8:10 am
Hi, I've install Amahi as per standard installation. I have SuSE64 11.3 on my main machine and I'm trying to get NFS shares working from Amahi. The problem is the NFS client setup hangs on suse, this has worked fine with other NFS servers. Which leads me to believe I missed something in the Amahi NFS server setup.
Currently the error on suse on the NFS client setup is "Unable to mount share in fstab", which is 'hda.skynet:/home/steve/Public /home/test nfs defaults 0 0' .
I tested the addressing with 'smb://hda.skynet/Music' which appeared to fine. So this is what I did to arrive at this error, perhaps you spot what I missed (please it driving me nuts
)
On amahi (borrowed from forum article ). Here I'm working from my suse box and ssh to Amahi, I wanted joe as my editor and setup the NFS as server...
in /etc/exports I've added some test lines..
Then I cranked up the NFS service..
Went to the Services screen and checked NFS service is running ok. So far so good.
On the machine I went to Yast/NFS Client and removed the old links and added 'hda.skynet', '/home/steve/Public' to mount point '/home/test', okay. Suse hangs for a long time and bugs out. If I restart the NFS client I get this message...
suse64:/home/steve/Desktop # rcnfs restart
Shutting down NFS client services: idmapd done
Starting NFS client services: sm-notify idmapd done
Message from syslogd@suse64 at Dec 1 15:02:12 ...
I then changed the RIP version from "4 and 6", to 4 only, and I set NFS version back to 4 only... still cant get Suse to see the NFS shares on Amahi. I've tested the Suse client on with other machines and its working, the only thing thats changed is using Amahi as the NFS and DCHP server. And yes the firewalls are off and there all on the same router. Any ideas please before I'm force to abandon this?
Currently the error on suse on the NFS client setup is "Unable to mount share in fstab", which is 'hda.skynet:/home/steve/Public /home/test nfs defaults 0 0' .
I tested the addressing with 'smb://hda.skynet/Music' which appeared to fine. So this is what I did to arrive at this error, perhaps you spot what I missed (please it driving me nuts
) On amahi (borrowed from forum article ). Here I'm working from my suse box and ssh to Amahi, I wanted joe as my editor and setup the NFS as server...
Code: Select all
steve@suse64:~/Desktop> ssh root@hda.skynet
[root@skynet ~]# yum install joe
[root@skynet ~]# joe /etc/exports Code: Select all
/var/hda/files/music/ *(rw,no_root_squash)
/home/steve/Public *(rw,no_root_squash)Code: Select all
[root@skynet ~]# chkconfig nfs --level 2345 on
[root@skynet ~]# service nfs restartOn the machine I went to Yast/NFS Client and removed the old links and added 'hda.skynet', '/home/steve/Public' to mount point '/home/test', okay. Suse hangs for a long time and bugs out. If I restart the NFS client I get this message...
suse64:/home/steve/Desktop # rcnfs restart
Shutting down NFS client services: idmapd done
Starting NFS client services: sm-notify idmapd done
Message from syslogd@suse64 at Dec 1 15:02:12 ...
Code: Select all
kernel:[ 3964.283848] last sysfs file: /sys/devices/virtual/bdi/0:19/uevent
suse64:/home/steve/Desktop #
Message from syslogd@suse64 at Dec 1 15:02:12 ...
kernel:[ 3964.284026] Stack:
Message from syslogd@suse64 at Dec 1 15:02:12 ...
kernel:[ 3964.284050] Call Trace:
Message from syslogd@suse64 at Dec 1 15:02:12 ...
kernel:[ 3964.284054] Inexact backtrace:
Message from syslogd@suse64 at Dec 1 15:02:12 ...
kernel:[ 3964.284056]
Message from syslogd@suse64 at Dec 1 15:02:12 ...
kernel:[ 3964.284208] Code: Bad RIP value.
Message from syslogd@suse64 at Dec 1 15:02:12 ...
kernel:[ 3964.284223] CR2: 0000000000000000