How to change the FSINFO for nfsd?
Hi,
Currently a gentoo linux server is used as a nfs server for some Mac OS X clients. These Mac OS X clients are doing video editing.
Currently the video are captured directly to the NFS mounts.
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).
The link about the above information can be found at this link below. Read towards the bottom of the link.
http://forums.creativecow.net/thread/8/975362
I really would like to know where to change in the NFS source code so that the FSINFO response from the server in which the max file size is set to 'FFFF FFFF FFFF FFFF' (all '1's).
P.V.Anthony
Quoted 16 lines · P.V.Anthony
Hi,
Currently a gentoo linux server is used as a nfs server for some Mac OS X clients. These Mac OS X clients are doing video editing.
Currently the video are captured directly to the NFS mounts.
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).
Quoted 7 lines
The link about the above information can be found at this link below. Read towards the bottom of the link.
http://forums.creativecow.net/thread/8/975362I really would like to know where to change in the NFS source code so that the FSINFO response from the server in which the max file size is set to 'FFFF FFFF FFFF FFFF' (all '1's).
You're really stabbing in the dark, here. I suggest you email the software manufacturer of Final Cut Pro (Apple?) with a support request.
Thanks,
Jeff
Quoted 2 lines · Jeff Moyer
You're really stabbing in the dark, here. I suggest you email the software manufacturer of Final Cut Pro (Apple?) with a support request.
You are right but Apple is not going to help because I am using Linux. They would ask me to buy a Apple Xserve.
I know it will work because the commercial company made the changes and it works. I also understand that they will not share the code change because it is a commercial thing.
Here is their email. At least they are willing to share this. -------------- start ----------------------
Yes we arrive to an interesting conclusion. Over NFS the Max OSX10.5 client uses the NFS FSINFO request to discover NFS server capabilities such as the max file size. Specifically Mac NFS servers return a value of all '1's for the max file size field in the FSINFO response. This value is not realistic but tell the Mac client that this is a Mac NFS server that can handle files larger then 2GB.
We are a storage vendor so we changed the code for our NFS server to return the same FSINFO information and that resolved the file chopping problem. It also fixed another bug where copies over the finder of files over 4GB failed. Now they don't.
-------------- end ----------------------
If possible, please share how to change the code to make the FSINFO present all '1's for the max file size field.
P.V.Anthony
Ian Kent
maintainerQuoted 27 lines · P.V.Anthony
Quoted 2 lines · Jeff Moyer
You're really stabbing in the dark, here. I suggest you email the software manufacturer of Final Cut Pro (Apple?) with a support request.
You are right but Apple is not going to help because I am using Linux. They would ask me to buy a Apple Xserve.
I know it will work because the commercial company made the changes and it works. I also understand that they will not share the code change because it is a commercial thing.
Here is their email. At least they are willing to share this. -------------- start ----------------------
Yes we arrive to an interesting conclusion. Over NFS the Max OSX10.5 client uses the NFS FSINFO request to discover NFS server capabilities such as the max file size. Specifically Mac NFS servers return a value of all '1's for the max file size field in the FSINFO response. This value is not realistic but tell the Mac client that this is a Mac NFS server that can handle files larger then 2GB.
We are a storage vendor so we changed the code for our NFS server to return the same FSINFO information and that resolved the file chopping problem. It also fixed another bug where copies over the finder of files over 4GB failed. Now they don't.
Quoted 4 lines
-------------- end ----------------------
If possible, please share how to change the code to make the FSINFO present all '1's for the max file size field.
This isn't the place to ask how to make changes to the kernel NFS client. You should probably ask this on the linux-nfs list.
Ian
Quoted 2 lines · Ian Kent
This isn't the place to ask how to make changes to the kernel NFS client. You should probably ask this on the linux-nfs list.
Thank you for the information. I will try there.
P.V.Anthony