Hi,
I've never been using NFS before, but I'm going to need it. I gathered some documentation (Deployment Guide, RHEL 5 Unleashed, general NFS docs) and I have a few machines to experiment with.
After about two hours of reading and experimenting, I must admit the documentation is confusing, to say the least. Although some step-by-step tutorials are provided, none of them work. For example, the RHEL deployment guide mentions NFSv2, NFSv3 and NFSv4... but as much as I poke around, I don't even find a way to checkout which one of the version I'm running.
So...
1) Can you suggest some reliable and well-written (think: newbie-friendly) documentation about NFS?
2) Usually I start out from a minimal install on desktop as well as servers. Which packages are needed on the servers side, and on the client side, in order for NFS to work correctly? None of the docs mentioned above says a word about it.
Thanks,
Niki
On Sat, 04 Jul 2009 10:02:44 +0200 Niki Kovacs wrote:
- Can you suggest some reliable and well-written (think:
newbie-friendly) documentation about NFS?
There isn't much to setting up a simple NFS fileserver and client mount. Set up /etc/exports on the server (this assumes your client is 192.168.0.3)
/whatever/where-ever/ 192.168.0.3(rw)
Start the nfs service. Create a mount point on the client
"mkdir /mnt/fileserver"
then mount the fileserver there.
"mount fileserver:/whatever/where-ever/ /mnt/fileserver"
Frank Cox a écrit :
There isn't much to setting up a simple NFS fileserver and client mount. Set up /etc/exports on the server (this assumes your client is 192.168.0.3)
/whatever/where-ever/ 192.168.0.3(rw)
Start the nfs service. Create a mount point on the client
"mkdir /mnt/fileserver"
then mount the fileserver there.
"mount fileserver:/whatever/where-ever/ /mnt/fileserver"
OK, I made a fresh start on this and installed two vanilla CentOS 5.3 systems (GNOME desktops, no tweaks or whatsoever) on two sandbox machines in my LAN. Everything works all right, out of the box, like a charm.
Now I'd like to explore things NFS a little further, and the next question is: starting from a bare bones minimal system, what packages do I need to make NFS work a) on the server side, and b) on the client side? For example, in order to use DHCP on my network, I installed the dhcp package for a DHCP server, and then on the clients I'm using dhclient (already included in the minimum base install).
I have quite some documentation here for CentOS / RHEL, but curiously enough, none seems to mention the needed packages to make NFS work.
The reason I'm asking: usually I like to install only what's needed.
Any suggestions ?
Niki
The tool you need is nfs-utils, if you do a # rpm -qi --provides nfs-utils you will get output of which software it provides, and some info about the package. Most of the nfs service is handled by the kernel: "Summary : NFS utlilities and supporting clients and daemons for the kernel NFS server."
I hope this helps you one step further
Sander
Niki Kovacs wrote:
Frank Cox a écrit :
There isn't much to setting up a simple NFS fileserver and client mount. Set up /etc/exports on the server (this assumes your client is 192.168.0.3)
/whatever/where-ever/ 192.168.0.3(rw)
Start the nfs service. Create a mount point on the client
"mkdir /mnt/fileserver"
then mount the fileserver there.
"mount fileserver:/whatever/where-ever/ /mnt/fileserver"
OK, I made a fresh start on this and installed two vanilla CentOS 5.3 systems (GNOME desktops, no tweaks or whatsoever) on two sandbox machines in my LAN. Everything works all right, out of the box, like a charm.
Now I'd like to explore things NFS a little further, and the next question is: starting from a bare bones minimal system, what packages do I need to make NFS work a) on the server side, and b) on the client side? For example, in order to use DHCP on my network, I installed the dhcp package for a DHCP server, and then on the clients I'm using dhclient (already included in the minimum base install).
I have quite some documentation here for CentOS / RHEL, but curiously enough, none seems to mention the needed packages to make NFS work.
The reason I'm asking: usually I like to install only what's needed.
Any suggestions ?
Niki _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Sander Snel a écrit :
The tool you need is nfs-utils, if you do a # rpm -qi --provides nfs-utils you will get output of which software it provides, and some info about the package. Most of the nfs service is handled by the kernel: "Summary : NFS utlilities and supporting clients and daemons for the kernel NFS server."
I hope this helps you one step further
Yes! I just got it working on two minimal installs. Looks like server as well as client need the nfs-utils package, as it contains the mount.nfs and umount.nfs commands.
Cheers,
Niki
On Sat, 2009-07-04 at 10:02 +0200, Niki Kovacs wrote:
For example, the RHEL deployment guide mentions NFSv2, NFSv3 and NFSv4... but as much as I poke around, I don't even find a way to checkout which one of the version I'm running.
--- That's because you have to specify what version of nfs you want or it defaults to what is installed on the server. See man nfs and man exports.
It is in the man page which is astonishing to me.
john
JohnS a écrit :
It is in the man page which is astonishing to me.
Neither 'man nfs' nor 'man exports' specify any version. But I tried again to mount the NFS share, this time by specifying a filesystem, like this:
# mount -t nfs4 raymonde:/data /home/shares
Here's what I got this time:
Warning: rpc.idmapd appears not to be running. All uids will be mapped to the nobody uid.
... and I didn't get a shell prompt back, so something didn't quite work out. I conclude that there's some daemon missing on the client (like I said, I always start out from a minimal configuration and then add packages as needed). Any idea what package rpc.idmapd belongs to, because a search with 'yum provides' and 'yum search' showed nothing.
Niki
On Sat, 2009-07-04 at 10:46 +0200, Niki Kovacs wrote:
JohnS a écrit :
It is in the man page which is astonishing to me.
Neither 'man nfs' nor 'man exports' specify any version. But I tried again to mount the NFS share, this time by specifying a filesystem, like this:
# mount -t nfs4 raymonde:/data /home/shares
Here's what I got this time:
Warning: rpc.idmapd appears not to be running. All uids will be mapped to the nobody uid.
... and I didn't get a shell prompt back, so something didn't quite work out. I conclude that there's some daemon missing on the client (like I said, I always start out from a minimal configuration and then add packages as needed). Any idea what package rpc.idmapd belongs to, because a search with 'yum provides' and 'yum search' showed nothing.
Niki _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi
Things that control nfs on the server are
1. /etc/sysconfig/nfs no modifications required for me 2. /etc/exports see mine below 3. firewall settings mine is off 4. /etc/idmapd.conf if using nfs4 - an nfs4 domain is required 5. /etc/fstab probably bind mounts needed - if using nfs4
First decision is whether to use nfs4 or not - this exports works for both on mine The mount command on the client is different in the two case nfs4 mount -t nfs4 maui:/global /global
nfs3 mount maui:/exports/global /global --------------------------------------------------- maui.jaa.org.uk sysconfig 3# cat /etc/exports /exports 148.197.29.0/24(rw,insecure,sync,wdelay,no_subtree_check,no_root_squash,fsid=0) /exports/global 148.197.29.0/24(rw,insecure,sync,wdelay,no_subtree_check,nohide,no_root_squash) /exports/home 148.197.29.0/24(rw,insecure,sync,wdelay,no_subtree_check,nohide,no_root_squash) --------------------------------------------------- bind mounts for nfs4 maui.jaa.org.uk sysconfig 4# cat /etc/fstab LABEL=home_maui /home ext3 defaults 1 2 LABEL=global_maui /global ext3 defaults 1 2 /home /exports/home none bind 0 0 /global /exports/global none bind 0 0 --------------------------------------------------- maui.jaa.org.uk sysconfig 5# cat /etc/idmapd.conf [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs #Domain = localdomain Domain = jaa.org.uk [Mapping] Nobody-User = nfsnobody Nobody-Group = nfsnobody [Translation] Method = nsswitch --------------------------------------------------- maui.jaa.org.uk sysconfig 6# ps -ef|grep -i rpc root 2380 1 0 Jul02 ? 00:00:00 rpc.idmapd --------------------------------------------------- [root@maui ~]# service rpcidmapd status rpc.idmapd (pid 2380) is running... ---------------------------------------------------
On the client (F11 in my case) The default /etc/idmapd.conf should work if the nfs4 domain is the same as the DNS domain - if in doubt force them to be the same on both the server and the client The nfsnobody ownership is probably the result of the server and client domain not being the same (and/or idmapd not running on both server and client) /etc/idmapd.conf naxos ~ 1# cat /etc/idmapd.conf [General] #Verbosity = 0 # The following should be set to the local NFSv4 domain name # The default is the host's DNS domain name. #Domain = local.domain.edu Domain = jaa.org.uk ...
Hope this helps
John
-
Frank Cox -
John Austin -
JohnS -
Niki Kovacs -
Sander Snel