views:

272

answers:

3

I set up an NFS server on my CentOS box with this for the /etc/exports file:

/var/www 192.168.0.0/24(rw,sync,no_root_squash)

Then on my Ubuntu machine, I ran:

# cd ~/
root@bill-murray:~# mount -v 192.168.0.21:/var/www ash
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar  5 13:27:59 2009
mount.nfs: text-based options: 'addr=192.168.0.21'
mount.nfs: internal error

I've wracked my brain trying to figure out what is causing the problem. Any ideas?!

+1  A: 

Is the CentOS box running an NFS server? It also looks like you might have a bad network setup - that reference to "addr=216.27.xxx.xx" makes me think that it's trying to use the external interface.

Paul Tomblin
A: 

192.168.0.0/24 is from 192.168.0.0 to 192.168.0.255 What's the address of 216.27.xxx.xx doing?

Andy
+1  A: 

See this: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444

So, if your CentOS box is running the same nfs-kernel-server that is in Ubuntu, you got troubles. You may have to drop back to an earlier version.

I find it absolutely astounding that the bug appeared in Ubuntu 8.04 (April 2008) and at this writing has yet to be fixed in Ubuntu. Debian has a fix.