HOWTO: NFS Server/Client

[dmizer]

Here is the client's /etc/fstab:

Actually, I need the server's /etc/fstab to see the how the disks are mounted on the server.

Still doing the same thing. It keeps spitting out errors about not being able to find the ports. I checked everything. I'm at wits end. Why is it so hard to netboot something?

Did you install portmap?

sudo apt-get install portmap

[NeilR]

Actually, I need the server's /etc/fstab to see the how the disks are mounted on the server.

Here ya go! Server's /etc/fstab

proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/mapper/FSUBSV1004-root /               ext4    errors=remount-ro 0       1
UUID=9eb59e31-794a-476f-8992-6a79e12b9be9 /boot           ext2    defaults        0       2
/dev/mapper/FSUBSV1004-swap_1 none            swap    sw              0       0
/dev/sdb1  /mnt/disks/disk2  ext4  nosuid,noexec,nodev  0  1
/dev/sdc1  /mnt/disks/disk3  ext4  user,nosuid,noexec,nodev  0  0

[xPreatorianx]

Actually, I need the server's /etc/fstab to see the how the disks are mounted on the server.



Did you install portmap?

sudo apt-get install portmap

Yes portmap is installed. RPCinfo says it is working as well from my previous logs. At least I guess rpcinfo is saying it's working. Hell I don't know how to read half of these logs. So I have no idea lol.

EDIT: See?

prea@prea-dev:~$ rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  59496  status
    100024    1   tcp  58250  status
    100021    1   udp  37426  nlockmgr
    100021    3   udp  37426  nlockmgr
    100021    4   udp  37426  nlockmgr
    100021    1   tcp  33013  nlockmgr
    100021    3   tcp  33013  nlockmgr
    100021    4   tcp  33013  nlockmgr
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049
    100227    3   tcp   2049
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049
    100227    3   udp   2049
    100005    1   udp  47827  mountd
    100005    1   tcp  50681  mountd
    100005    2   udp  47827  mountd
    100005    2   tcp  50681  mountd
    100005    3   udp  47827  mountd
    100005    3   tcp  50681  mountd

[xeddog]

I have seen many people having issues with an access denied error when trying to mount an nfs share and I thought I would just add my experience. I have been trying to get my Popcorn Hour mounted using nfs and could not seem to get past the access denied error UNTIL I added nfsvers=3 to the end of the line in fstab like this:

Popcorn:/share	/media/Popcorn nfs rw,rsize=8192,wsize=8192,intr,nfsvers=3

After adding that it works fine.

For reference, the Popcorn Hour runs some flavor of Linux, and my computer is running Ubuntu Maverick.

Wayne

[xPreatorianx]

Still getting the exact same errors :S. This is extremely frustrating.

[Jose Catre-Vandis]

@ NeilR

You don't have an nfs mount point in your clients fstab file - won't work without one

anyway:

This is how I do it, with a server with 4 disks in it. You do some of the work on the client side, so perhaps not quite what your after (?) but it works.

Server

fstab

/dev/sda1 /mnt/disk1
/dev/sdb1 /mnt/disk2
/dev/sdc1 /mnt/disk3
/dev/sdd1 /mnt/disk4

exports (10.10.10.1 is my subnet, so the commands server all Pcs on that subnet)

/mnt/disk1 10.10.10.1/24(rw,no_root_squash,async,no_subtree_check)
/mnt/disk2 10.10.10.1/24(rw,no_root_squash,async,no_subtree_check)
/mnt/disk3 10.10.10.1/24(rw,no_root_squash,async,no_subtree_check)
/mnt/disk4 10.10.10.1/24(rw,no_root_squash,async,no_subtree_check)

Client

directories:

/mnt
/mnt/disks
/mnt/disks/disk1
/mnt/disks/disk2
/mnt/disks/disk3
/mnt/disks/disk4

fstab (10.10.10.70 is my server IP)

10.10.10.70:/mnt/disk1 /mnt/disks/disk1 nfs rsize=8192,wsize=8192,timeo=14,intr,bg
10.10.10.70:/mnt/disk2 /mnt/disks/disk2 nfs rsize=8192,wsize=8192,timeo=14,intr,bg
10.10.10.70:/mnt/disk3 /mnt/disks/disk3 nfs rsize=8192,wsize=8192,timeo=14,intr,bg
10.10.10.70:/mnt/disk4 /mnt/disks/disk4 nfs rsize=8192,wsize=8192,timeo=14,intr,bg

I always use IP addresses to avoid translation problems, and a word of warning, this is on a server running Jaunty / nfs3, so your experience might be different!

However, your client should end up with a folder "disks" with disks 1-4 inside it, all mounted

[Jose Catre-Vandis]

@ xPretorianx

You haven't got another dhcp server running somewhere - e.g. on your router?

Have you tried netbooting a PC as opposed to a PS3, just to eliminate that variable?

Also, can you boot up a LIVE CD or similar on the PS3, and try a more straight forward NFS share scenario? Might give some pointers ? (Like the first page of this howto)

Try fixing all your IP addresses, it looks like you are using IP addresses throughout (as opposed to hostnames)

Review the versions of NFS running / expected, read back a couple of pages on this thread for some detail about this.

[NeilR]

Jose,

Thanks for the suggestion. That was exactly the work-around I mentioned in my first post (but did not elaborate). Even the names are the same

I liked my first idea because it would eliminate the need to modify the client fstab files when new drives are added. Also I was just curious if that higher level mount could work. Apparently not, and it's not worth any more effort.

[dmizer]

Yes portmap is installed. RPCinfo says it is working as well from my previous logs. At least I guess rpcinfo is saying it's working.

Have you tried directly mounting these NFS shares (rather than trying to do a net-boot)? If the shares work directly, then the problem is with your LTSP server configuration.

Jose,

Thanks for the suggestion. That was exactly the work-around I mentioned in my first post (but did not elaborate). Even the names are the same

I liked my first idea because it would eliminate the need to modify the client fstab files when new drives are added. Also I was just curious if that higher level mount could work. Apparently not, and it's not worth any more effort.

I have been busy so I haven't done much work on this yet. I have found nothing anywhere which indicates that it's impossible to do what you want to do. I looked at a lot of NFS documentation and found nothing yet. So, I plan to try your configuration on my server at home.

[Jose Catre-Vandis]

Jose,

Thanks for the suggestion. That was exactly the work-around I mentioned in my first post (but did not elaborate). Even the names are the same

I liked my first idea because it would eliminate the need to modify the client fstab files when new drives are added. Also I was just curious if that higher level mount could work. Apparently not, and it's not worth any more effort.

I am not sure why it doesn't work for you (the way you want to do it). I have been able to nfs share the whole root system that all my other nfs shares are mounted to on the server, and that works OK. I know that you can't symlink directories and nfs share them....Try mounting all the disks directly to /mnt and then try sharing /mnt, (you don't necessarily need the /mnt/disks directory), see what happens. Go back and check your exports file again, and make sure everything is right.

Sorry the above is wrong, any nfs mounts don't show up
(I used the same names for everything to remove confusion )