nfs issues

cwwilson721 · 05-11-2006, 11:01 PM

I'm trying to mount a nfs share on my server.
I keep getting a 'RPC: Timed out" error.

I noticed during a reboot of the sever that it 'hangs' for 2 min + at "/sbin/exportfs -r"

Here is the server output of /etc/exports:

Code:

# cat /etc/exports
/mv/ *(rw,async)
/slack/ *(rw,async)

ps aux says that all the crud in /etc/rc.portmap is running.

I was able earlier this week to connect/mount both shares, now it usually does not mount either, or only the /slack one.

Here is /etc/fstab on the local machine:

Code:

$ cat /etc/fstab
/dev/hda3        swap             swap        defaults         0   0
/dev/hda1        /                ext3        defaults         1   1
/dev/hda2        /root            ext3        defaults         1   2
/dev/cdrom       /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
dads://slack     /mnt/slack       nfs         auto,users,rw    1   1
dads://mv        /mnt/mv          nfs         auto,users.rw   1   1

When I try :

Code:

/etc/rc.d/rc.nfsd restart

it hangs forever with this:

Code:

# /etc/rc.d/rc.nfsd start
Starting NFS services:
  /usr/sbin/exportfs -r

And that's it.

I'll post anything else relevant.

Local machine:
Kernel 2.6.17-rc3
Slackware-current (Clean install from local mirror)

Server:
Kernel 2.6.13
Slackware 10.2

Any ideas will be appreciated.

Bruce Hill · 05-12-2006, 03:05 AM

Please read this and see if you can determine where you configured wrong.

If that doesn't help, you might want to consider that Slackware -current and that kernel you're running are for testing, not for production work. But -current is meant to be tested to get the bugs out - and bugs is what you find. Bugs, and incompatibilities, and "too" bleeding edge programs. The stable releases are for the people who actually want work done

I say this not to criticize you, but to share some of what I've lately experienced. At the present moment I can't even mount a flash disk or camera anymore --- running:

Code:

mingdao@silas:~$ cat /etc/slackware-version
Slackware -current
mingdao@silas:~$ uname -a
Linux silas 2.6.16.14 #1 Mon May 08 14:59:39 CST 2006 i686 athlon-4 i386 GNU/Linux

I'm at the present time taking 5 computers back to Slackware-10.2 and 2.6.16. That's the last combination that gave me no troubles.

I have one box that is for testing only, and I'll let the blood drain from it.

cwwilson721 · 05-12-2006, 03:21 AM

Actually, when I noticed that it would only mount one of the exports, I just 'rearranged' stuff, so now it works fine.

The client is running Current and 2.6.17-rc3, the server is running 10.2 and 2.6.13. Both are very stable.

Thanks for the reply and the links. What I did was copied the /mv directory into /slack, now everything is ok.

I'll get it figured out later on why the server 'hangs' where it does.

Bruce Hill · 05-12-2006, 03:25 AM

I run Samba and NFS on my server, following Eric's instructions, and it doesn't hang. You might want to check -- yours is setup a bit differently.

This line has a . instead of a , --- don't know if you copied and pasted or typed.

Quote:

dads://mv /mnt/mv nfs auto,users.rw 1 1

Bruce Hill · 05-12-2006, 03:29 AM

Also, from "man fstab" ---

Quote:

The sixth field, (fs_passno), is used by the fsck(8) program to determine the order
in which filesystem checks are done at reboot time. The root filesystem should be
specified with a fs_passno of 1, and other filesystems should have a fs_passno of
2. Filesystems within a drive will be checked sequentially, but filesystems on
different drives will be checked at the same time to utilize parallelism available
in the hardware. If the sixth field is not present or zero, a value of zero is
returned and fsck will assume that the filesystem does not need to be checked.

Don't know the real significance of that.