From: Christoph Hellwig <hch@infradead.org>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] statfs fails with EOVERFLOW
Date: Tue, 23 Mar 2004 13:36:07 +0000 [thread overview]
Message-ID: <20040323133607.A473@infradead.org> (raw)
In-Reply-To: <20040323133019.GD30984@suse.de>; from okir@suse.de on Tue, Mar 23, 2004 at 02:30:19PM +0100
On Tue, Mar 23, 2004 at 02:30:19PM +0100, Olaf Kirch wrote:
> > that's why we have statfs64 in 2.6, a program with the right LFS magic
> > and a recentish glibc should use if for you.
>
> The glibc maintainers at suse tell me it's broken at the moment.
>
> Second, not all apps can easily be converted to LFS support. One of the
> apps that barfed was OpenOffice... be my guest and make it LFS clean :)
OpenOffice is hopeless, it's one of this "if it's finally unmaintainable,
opensource it" things :)
> And finally, I think it's really an NFS bug. A local statfs on the file
> system on the server works fine; it's just that the NFS client barfs
> because it uses wtmult as the block size (and if it's a v2 mount, things
> are even worse because it picks a totally arbitrary wtmult value of 512).
Hmm. Why do you limit the sb_blocksize changes to 32bit architectures then?
I see it doesn't trip easily for 64bit arches, but having different values
for exactly the same filesystem and mount options sounds like a rather bad
idea to me.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-03-23 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 13:05 [PATCH] statfs fails with EOVERFLOW Olaf Kirch
2004-03-23 13:21 ` Christoph Hellwig
2004-03-23 13:30 ` Olaf Kirch
2004-03-23 13:36 ` Christoph Hellwig [this message]
2004-03-23 16:25 ` 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=20040323133607.A473@infradead.org \
--to=hch@infradead.org \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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.