public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "P.V.Anthony" <pvantony@singnet.com.sg>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org
Subject: Re: Solved - How to change the FSINFO for nfsd?
Date: Tue, 20 May 2008 01:59:50 +0800	[thread overview]
Message-ID: <4831C016.8000207@singnet.com.sg> (raw)
In-Reply-To: <20080519172412.GL7622@fieldses.org>

J. Bruce Fields wrote:
> On Sat, May 17, 2008 at 02:36:42PM -0400, Trond Myklebust wrote:
>> On Sat, 2008-05-17 at 20:25 +0200, Jan Engelhardt wrote:
>>> On Saturday 2008-05-17 19:57, P.V.Anthony wrote:
>>>> resp->f_properties = NFS3_FSF_DEFAULT;
>>>>
>>>> nfserr = fh_verify(rqstp, &argp->fh, 0, MAY_NOP);
>>>> @@ -570,7 +570,7 @@
>>>> if (sb->s_magic == 0x4d44 /* MSDOS_SUPER_MAGIC */) {
>>>> resp->f_properties = NFS3_FSF_BILLYBOY;
>>>> }
>>>> - resp->f_maxfilesize = sb->s_maxbytes;
>>>> + resp->f_maxfilesize = 0xffffffffffffffff;
>>    This is plain wrong! Pretending that your filesystem supports 64-bit
>> files won't magically make it so.
> 
> Yes.  Could you tell us what filesystem you're using?
> 
> It's a bit bizarre that this would fix anything; I'd think the more
> likely result would be errors on write and/or some kind of file
> corruption.

The filesystem used is ext3. So far no file corruption. The os is 64bit
gentoo.

Will be trying xfs without the patch and will report back. I think XFS
is 64bit and will see if Mac OS X with Final Cut Pro works with it.

Please not that the problem only happens when using the video editing
application Final Cut Pro. Without the patch, when capturing video to
the mounted NFS, the captured video is broken into 2Gb size files. This
is even when the server and client is set to version 3.

The old version of FCP does not have this behaviour.

I am guessing that Apple is some way forcing people to buy their Xserve
servers. To use their servers for NFS.

If a file is dragged on to the NFS mount then it will work fine. It only
does not work through the FCP application. Like when capturing or
exporting to a NFS mount.

P.V.Anthony



  reply	other threads:[~2008-05-19 18:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 17:05 How to change the FSINFO for nfsd? 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
2008-05-17 17:57   ` Solved - " P.V.Anthony
2008-05-17 18:25     ` Jan Engelhardt
2008-05-17 18:36       ` Trond Myklebust
2008-05-19 17:24         ` J. Bruce Fields
2008-05-19 17:59           ` P.V.Anthony [this message]
2008-05-20  8:15           ` P.V.Anthony
2008-05-20 13:12             ` Trond Myklebust

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=4831C016.8000207@singnet.com.sg \
    --to=pvantony@singnet.com.sg \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox