public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "P.V.Anthony" <pvantony@singnet.com.sg>, linux-kernel@vger.kernel.org
Subject: Re: Solved - How to change the FSINFO for nfsd?
Date: Mon, 19 May 2008 13:24:12 -0400	[thread overview]
Message-ID: <20080519172412.GL7622@fieldses.org> (raw)
In-Reply-To: <1211049402.7498.4.camel@localhost>

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.

--b.

  reply	other threads:[~2008-05-19 17:24 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 [this message]
2008-05-19 17:59           ` P.V.Anthony
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=20080519172412.GL7622@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvantony@singnet.com.sg \
    --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