• firewall behavior
• exporting file system syntax and use of pseudo file systems
• difference in mount command syntax

I am running systems that use SELinux and firewalls*. I have one Centos 5.3 NFS server and three client machines running as virtual machines** on the server. My goal was to establish remote file systems for the virtual machine clients. I’ll skip some of the introductory steps to set up the nfs server process that are listed in the doc.

I’ll list the commands that I used to export the file system from the server and the mount command I first used on the client. The file system that I was attempting to export was /junk/client1. On the server (server.stevens.net), I added the following to /etc/exports:

and I used the following mount command on client1.stevens.net (and received the error shown):

A bit surprised that it didn’t work, I poked around the Internet and I found some good info that ultimately helped me get on the right track at Miles Brennan’s Linux Home Server HOWTO page. He does an excellent job explaining the pseudo file system configuration required for version 4 of NFS.

I built out the following psuedo file system on the server:

I then created bindings in /etc/fstab between /NFS4exports and /junk directories as follows (Bindings are like symbolic links, but the files are available in both filesystems, rather than being linked to the source location.):

Then I list the pseudo file systems in the /etc/exports file, and it is critical to note that the fsid=0 option be defined on the /NFS4exports file system (even though /NFS4exports itself will not be mounted by a remote client). Then all exported file systems are sub-directories of this system. If I had additional file systems elsewhere on the server that I wanted to share (say, /home), I would need to create an entry in the pseudo file system and bind it to /home in fstab.

Then I mounted the file systems from the client1 system. A major difference between the NFSv3 and NFSv4 command is that the root pseudo filesystem is not included in the identity of the remote file system (i.e., the NFS4exports directory is omitted from the command.

And on client2, showing an example that it can mount the client1 directory, but can’t see anything or write to it:

And that completed my setup (except to modify /etc/fstab so that the new /remotesys file system will automount at boot). The main point was to learn about NFS, but I also ended up with a way to provide storage for my virtual machines outside of the .vmdk virtual file system.


Footnotes:
* NFSv4 plays better with firewall because, unlike NFSv3, it does not make use of portmapper and rpc.mountd, rpc.statd, and rpc.lockd. I just had to open port 2049 on the firewall for NFS. However, during some troubleshooting, I needed to execute “showmount -e sserver.stevens.net’ from a client machine. The firewall blocked it, because it uses rpc.mountd and portmapper picks a random port by default. I used /etc/sysconfig/nfs to define a static port for rpc.mountd and then opened this port on the firewall too.
** As a side note with respect to the virtualization setup, I created one vm and installed a small, simple Centos image. Then I copied the files twice to new folders in /var/lib/vmware/VirtualMachines. Then I imported these virtual machines into VMware Server to quickly make some clones. Just a quick edit of the /etc/sysconfig/network file to update each machine to a unique hostname, and I had 3 distinct client machines.

Then reboot the system, and make and mount the volumes.

Now, This volume will be used only as a Samba share. As discussed here by Walker, we do not need to reserve block space for the root user or system logs. Here is how to adjust it:

Ta-da! Now, on to a Logical Volumes. Logical volumes take more work to create and are more difficult to understand, but a quick read of Chapter 9 of the of the Redhat Deployment Guide will get you through. However, the deployment guide does not have a quick command line guide for creating LVMs.
I’m going to make a logical volume group VolGroup02, with two logical volumes, LogVol00 and LogVol01, each logical volume will be 100GB. I’ll start with the creation of the physical partition /dev/sdb2 using fdisk.

Then initialize the physical volume for use by LVM, create the Volume Group and Logical Volumes.

Then create the file systems, remove the reserved the space, make and mount the file systems.

And it is almost that easy. I did have some problems at the outset of this endeavor. After I installed the 500GB drive, I re-installed Linux (for an unrelated reason). I had thought that the installation ignored the 500GB drive, however, I learned that the installation process will allocate all unused space into a logical volume. I was confused at first when it would not make the filesystem, citing that it was in use. The folks over at the centos.org forum were able to help me out and get me on track.

So, I have a Linux machine with tons of HDD storage space (250 + 500 GB) .  The XP machine needs additional space.  And it must be transparent to the rest of the family.  I used Samba to create file shares on the Linux machine, then created mapped network drives on the XP machine that connect automatically to the Linux machine’s HDDs at login.  It wasn’t hard, but did trip me up on a couple points.

Samba is an open source software package that allows Linux/Unix machines to participate in Windows networking as nodes in the Windows “Network Neighborhood” and therefore provide file sharing between Linux and Windows machines.  It was easy to install the Samba package on CentOS, using the Add/Remove software package from the desktop GUI, and included a GUI configuration tool for Samba.  The CentOS deployment guide provides good guidance for configuration, and the samba.org site provide an excellent extra level of detail for the software.  A couple of points to add that were key learnings for me:

1. The Samba GUI provides a simple, easy configuration tool for the basic samba config, identifying the workgroup name, shared volumes and users/passwords.  The manual config is accomplished via the smb.conf file in /etc/samba.  Manual edit of the conf file provides more options than the GUI, including logging level, source IP address filtering, and preventing access to home directory.  However, if you make changes to this conf file, then make changes to the config via the GUI, your manual changes to the conf file will be removed.  So make the simple GUI config changes first, get a functioning system, then tweak the configuration with vi edits of the smb.conf file.
2. Windows XP required that I set samba up with “user” authentication, not “share”, and I had to encrypt the passwords on the Samba config.  Windows would not attempt to make connections when Samba was configured with unencrypted passwords.

The Samba config was easier to config than the Windows XP side.  Once I had the Samba server running, I was able to go into “Network Neighborhood”, view the “workgroup nodes” and connect with the user/password set up in Samba.  Then I could map a drive letter to a share folder on the Linux box.  Easy, right?  Almost.  Even though I asked Windows to ‘reconnect at login’, Windows could not.  Looking at the Samba logs in var/log/samba/smbd.log (with logging set to level 3 via the conf file “log level = 3) I could tell that the problem was with XP, not Samba, and I suspect that Windows was not chaching the password.

The solution was a batch file that runs at startup on the XP machine.  I found a forum post that explained the syntax very well, using the net use command.  My specific command was “net use S: \\server\storage passwd /USER:username”  Then I just had to store the batch file in the ‘startup’ programs folder for “All Users”, and now the drive maps automatically at startup.  Then I’ll convert the “My Pictures” folder to a shortcut to a folder on the Samba shared volume.  Perfectly transparent to my family.

As long as the power is on the Linux box.

Update Jul 20, 2009:

I rebuilt my machine and used a firewall and Security Enhanced Linux (SELinux), which created a couple additional challenges.  First, the firewall had to be configured to allow smb protocol for Samba, which was easy.  Second, (and a bit more tricky) the smb.conf file had notes for SELinux, indicating that the shared folders needed to be marked with “samba_share_t”. The current labels can be displayed with “ls -ldZ /path”, and the label on a share folder can be set with “chcon -t samba_share_t /path”. Once I resolved these issues, all was fine.

Photo credit, eheçatzin

I downloaded the latest CentOS, 5.3 x86_64 (verified with a nice MD5 calculator from Microsoft), burned 7 .iso CD’s using our old PC, dropped disk 1 into the new PC’s DVD/CD drive, powered on and seemed to make some progress…but after a few text based screens realized that CentOS could not recognize my SATA HDD nor DVD/CD and would not launch the install GUI.  I was able to rig a connection between my old PC’s IDE CD drive to the new PC’s motherboard, changed boot preference in BIOS and was able to make better progress.  The install package would now launch its GUI, only to tell me that it could not find a HDD to partition.  Grrr…

I did some research on the web, and as with most things, I was not the first person to have this problem.  I was pretty sure it was an issue with my mobo/chipset and the SATA interface.  I was able to find a thread on the CenOS forum page that explained that I needed to type, at the boot prompt of the install: “linux pci=nomsi boot”.  Without really knowing what the command meant, I gave it a shot, and it worked.  I’ve since learned that I was preventing the use of Message System Interupts,  but don’t really understand yet why that fixed it.

I ran through a quick install and was pleased to get a booted PC, but quickly became dissapointed when I could not connect to the internet.  No Ethernet port discovered.  Back to the Centos forum.  I suspected an issue with the Ethernet controller, which was also on the chipset (nVidia GeForce 8300) and quickly found some advice that that fixed the problem.  I had to download a module using my old PC, transfer it to the new Linux box via USB stick sneakernet, and install it with rpm. A reboot of the PC (network services restart wasn’t enough), and I’m on the internet.  W00t!

By the end of the Memorial Day weekend, I had a functioning PC, ready for some more serious playing.  Maybe a second post later when I find additional components not recognized.