On Wed, May 7, 2008 at 10:41 PM, P.V.Anthony <[EMAIL PROTECTED]> wrote: > Here is the problem. The video files are broken into 2GB files. This > because the video editing software(Final Cut Pro) breaks the files into > 2GB sizes. It does not seem that the Mac OS X is not doing the breaking > up of files. It is the video editing software. > > Some commercial company found an interesting behaviour. All the Mac OS X > NFS server FSINFO response in which the max file size is set to 'FFFF > FFFF FFFF FFFF' (all '1's).
Just a thought, you might be mounting the NFS mount with NFS protocol version 2, which limits file reading to the first 2GB of the file (similarly with writing). Here is more info on that (search for maximum file size): http://nfs.sourceforge.net/ [1] Chris [1] Here is some of the more relevant FAQs (there is probably a better way to do this in OS X, but I have no experience with that): A1. What are the primary differences between NFS Versions 2 and 3? . . . Version 2 clients can access only the lowest 2GB of a file (signed 32 bit offset). Version 3 clients support larger files (up to 64 bit offsets). Maximum file size depends on the NFS server's local file systems. . . . A4. How can I prevent the use of NFS Version 2, or of other NFS versions? A. The protocol version is determined at mount time, and can be modified by specifying the version of the NFS protocol, or the version of the transport protocol, supported by the server. For example, the client mount command mount -o vers=3 foo:/ /bar will request that the server use NFS Version 3 when granting a mount request (Note that "vers" and "nfsvers" have the same meaning in the mount command; The string "vers" is compatible with NFS implementations on Solaris and other vendors). If you wish to prevent use of NFS Version 2 in all cases, then you must restart rpc.mountd on the server, with the option "-N 1 -N 2". The best way to do this is to modify the nfs rpc.mountd configuration on the server by modifying the NFS startup script options, and then shutting down and restarting NFS as a whole: * cd /etc/rc.d/init.d * Modify RPCMOUNTDOPTS in the nfs script to include "-N 1 -N 2" * Restart nfs (you must have root access) with "./nfs restart" You will now get the following error when attemping to nfs mount a file system using NFS Version 2 (now unrecognized) after restarting rpc.mountd: mount: RPC: Unable to receive; errno = Connection refused You will also subsequently get the following (non-fatal) warning when you unmount any nfs mounted file system at all, regardless of when it was mounted: Bad UMNT RPC: RPC: Program/version mismatch; low version = 3, high version = 3 _______________________________________________ Slugnet mailing list [email protected] http://wiki.lugs.org.sg/LugsMailingListFaq http://www.lugs.org.sg/mailman/listinfo/slugnet
