From: "P.V.Anthony" <pvantony@singnet.com.sg>
To: jmoyer@redhat.com
Cc: autofs@linux.kernel.org
Subject: Re: How to change the FSINFO for nfsd?
Date: Thu, 08 May 2008 08:49:22 +0800 [thread overview]
Message-ID: <48224E12.8010109@singnet.com.sg> (raw)
In-Reply-To: <x49skwunmju.fsf@dhcp-100-18-209.bos.redhat.com>
Jeff Moyer wrote:
> 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
next prev parent reply other threads:[~2008-05-08 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 14:37 How to change the FSINFO for nfsd? P.V.Anthony
2008-05-07 15:47 ` Jeff Moyer
2008-05-08 0:49 ` P.V.Anthony [this message]
2008-05-08 6:24 ` Ian Kent
2008-05-08 17:06 ` P.V.Anthony
-- strict thread matches above, loose matches on Subject: below --
2008-05-08 17:05 P.V.Anthony
2008-05-09 4:22 ` J. Bruce Fields
2008-05-11 16:44 ` P.V.Anthony
2008-05-11 17:36 ` Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48224E12.8010109@singnet.com.sg \
--to=pvantony@singnet.com.sg \
--cc=autofs@linux.kernel.org \
--cc=jmoyer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.