On Tue, 2007-11-20 at 20:25 -0800, Linda Walsh wrote: > I'm exporting some files (>10GB files) via NFS from a 2.6.23.1-kernel, > SuSE system, and mounting on another (same kernel). > > All of my files >2GB (not exactly sure if break point is at 2 or 4GB's, > all the large files I look at on the source are over 20G) give stat > errors over NFS. Both kernels have nfs v4 as well as v3 compiled in. > > I've heard v2 has a 2GB limit, but v3 should be fine. Have been > playing with tags 'nfsvers=[3 or 4]' in the /etc/exports file, but > exports doesn't recognize nfsver=4, and gives out of range error message > on nfsver=3 saying allowed values are Min=1, Max=2. !? I'm not sure if > it is using V3 or 4 (am trying to use 'tcp' tag as well, but not using > the tcp isn't the prob, as that was the default before I started looking > at this problem. > > I don't have problems over CIFS from a windows box, but so far, limited > benchmarks show better linux-to-linux perf over NFS (assuming I > stay under 2GB files, but that's sorta limiting...). > > Underlying filesystem on the server box is XFS -- been serving Win > clients for years, so haven't had alot of experience using NFS, recently, > since >2G files became fairly common place. > > Any ideas how I could be serving up NFS and not >2GB files with a modern > kernel and client? *scratching head* ;^? > > Thanks, > Linda > I routinely move files 3 to 4 Gbytes from xfs to jfs system with no problems. I am running the 2.6.22 kernel thugh and using open suse 10.3
Could you list the /etc/exports file and the rpms associated with the nfs server and the nfs client. Another thing you could do is to enable automount and uncomment the /net. There you can try to copy a large file say your machine is "hello" via "cp /net/hello/big.file /net/hello/big,file.copy" This will help to determine if your nfs server is properly configured. -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
