snicknet.net

So, I ran into an interesting problem last night while recording a 2hr long TV show, in case you’re wondering it was American Idol. So, as I began watching the recording all was well, when suddenly just around 1hr in the recording stopped and closed. Naturally I assumed something had crashed and tried once more, with the same result. Frustrated I checked the MythWeb, along with the clocks on my VM and frontend. Both were fine, then I turned my attention to the filesize of the recording. I noticed that the file system reported the file as being 2GB, and yet MythWeb thought it was 4.3GB. So, after doing a little research I discovered that the problem stemmed from my using an NFS share to store my recordings on my backend over the network. As it turns out, up to NFS version 2, there was a 2GB maximum filesize like FAT32. It appears based on my research that NFS should default to version 3 which supports larger file sizes, but after running the command: nfsstat -m, which will display your NFS info I was indeed using version 2. Upon further reading I discovered that I should have been using nfs-kernel-server and not nfs-user-server as my backend NFS server. So I swapped out one package for the other. Now with my newly installed nfs-kernel-server package installed I checked nfsstat -m again. The same result, still using version 2. Then I came across a small post online that outlined the same problem I was having it turns out you can force the NFS server to only accept certain versions of connections so the magic command for me was:

sudo nano /etc/init.d/nfs-kernel-server

Look for the RPCMOUNTDOPTS variable and add -N 1 -N 2 so it looks like: RPCMOUNTDOPTS=”-N 1 -N 2″

sudo /etc/init.d/nfs-kernel-server restart

Remount your shares on the remote client using “sudo mount -a” and double check nfsstat -m, you should now be using version 3 or 4 depending on how you setup your /etc/exports file on the NFS server. I’m presently using version 3 which has basically an identical entry line as to my earlier post for creating a share. Hope this helps somebody experiencing the same issue. Everything is recording beautifully tonight.