*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to export my FreeBSD home directories so that I can use them with the NIS setup I have (if there is a better/easier way please guide me to it ).
I have the following /etc/exports file on my freebsd machine:
Code:
/usr/home 192.168.7.10
Showmount on the client (Fedora Core 2) gives this:
Code:
# /usr/sbin/showmount -e 192.168.7.3
Export list for 192.168.7.3:
/usr/home 192.168.7.10
However when I try and mount it:
Code:
# mount 192.168.7.3:/usr/home /home
mount to NFS server '192.168.7.3' failed.
Why is it failing? Is it a client side issue or a sever side issue. It looks client side to me, but I just want to make sure.
# Rpcbind is used for all RPC services; protect your NFS!
# (IP addresses rather than hostnames *MUST* be used here)
rpcbind : 192.168.7.10/255.255.255.0 : allow
#rpcbind : 192.0.2.96/255.255.255.224 : allow
rpcbind : ALL : deny
It also struck me to run the mount command 'verbose'., and i got this:
Code:
# mount -v 192.168.7.3:/usr/home/frenchidyll /home/frenchidyll
mount: no type was given - I'll assume nfs because of the colon
mount to NFS server '192.168.7.3' failed.
RPC Error: 15 ( Program not registered )
Hope that helps... You assume right about the IP of my FC2 machine
I am totally stumpped as to how this is not working .... Well i don't have a FC2 machine to try and replicate the issue.
Will try to get a FC2 installation and see if i can replicate the same issue.
BTW can you do an NFS mount on another FreeBSD machine ,if you able to mount it successfully then this would rule out the possibility of wrong configuration on NFS server (192.168.7.3).
YAY! Success... it turns out that it was running, but it wasnt... rather confusingly.
`ps waux | grep nfsd` - showed 4 processes called nfsd, 1 master and 3 servers. But `rpcinfo -p localhost`didn't show any signs of nfs, so I ran `nfsd -u -t -n 4` which through a binding error about address *:udp.
So I decided to kill the existing nfsd processes and start nfsd up again, and wahlah! Four `kill -9`'s later and a nfsd start I was able to finally mount my NFS!
Thanks again for all your help! We got there in the end. Never discount the simple things
My situation was that I had one server, and I had two other systems (also servers) connecting to a volume on the one server. One system had the volume mounted (at least 2 months), and it was working perfectly. I just brought up the second system and was trying to connect to the same volume, and it wasn't letting me in (same problem reported above).
I did a "ps -ef | grep nfs" and they listed the processes, but they had square brackets around them, indicating zombie processes. So I restarted the daemon on the server "/etc/init.d/nfs restart", and all the sudden I was able to mount on the second system.
Also, for those who are wary of trying this with an existing mount, it didn't disrupt the first system's mount; it still appears to be working perfectly.
I don't pretend to be an expert on NFS, but this sounds like a bug to me. I mean, I expect that the NFS daemon will accept new connections no matter how long it's been since the last request. Can anybody tell us whether this is the way the NFS daemon is supposed to behave?
Incidentally, my configurations are:
Server: AMD Opteron 1218HE (2.6GHz)
4GB RAM
Supermicro H8SMi-2-O Motherboard
1 160GB Seagate Barracuda SATA Drive
2 750GB Seagate Barracuda SATA Drives (in mirrored RAID)
The first client system is identical to the above.
Second Client: AMD Opteron 1218HE (2.6GHz)
2GB RAM
Supermicro H8SSLi-2 Motherboard
1 160GB Seagate Barracuda SATA Drive
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.