From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, peter@chubb.wattle.id.au
Subject: Re: statfs64 missing
Date: 16 Oct 2002 16:16:33 +0200 [thread overview]
Message-ID: <shs7kgipiym.fsf@charged.uio.no> (raw)
In-Reply-To: <20021016140658.GA8461@averell>
>>>>> " " == Andi Kleen <ak@muc.de> writes:
> This problem already exists on 2.4. You can actually access NFS
> servers which have more than 2TB of disk space. NFS uses the
> local write size as block size. When you are lucky then
> 0xfffffffff*wsize is bigger than what your NFS server
> reports. If not you get wrong results. The only workaround
> currently is to increase wsize, but that has its limits too.
> Fixing it properly probably requires statfs64(). Any reason why
> this was not included in the sector_t patchkit ?
If fixing NFS is the main concern, and we're adding a new syscall,
could someone also add in an equivalent of the Solaris
etc. 'f_frsize'.
Reporting the underlying local filessystem block size can be of use
for some applications. On NFS this value usually differs from the
'optimal transfer block size' aka. f_bsize.
Cheers,
Trond
next prev parent reply other threads:[~2002-10-16 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 14:06 statfs64 missing Andi Kleen
2002-10-16 14:16 ` Trond Myklebust [this message]
[not found] ` <15789.64263.606518.921166@wombat.chubb.wattle.id.au>
2002-10-17 0:01 ` Andi Kleen
2002-10-17 19:41 ` Benjamin LaHaise
2002-10-18 0:19 ` [PATCH] statfs64 no longer missing Peter Chubb
2002-10-18 0:26 ` Benjamin LaHaise
2002-10-18 2:31 ` Andi Kleen
2002-10-18 3:27 ` Peter Chubb
2002-10-18 6:17 ` Andreas Dilger
2002-10-18 6:31 ` Andi Kleen
2002-10-18 6:41 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 20:28 statfs64 missing Steven French
2002-10-17 21:55 ` Andreas Dilger
2002-10-17 21:27 Petr Vandrovec
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=shs7kgipiym.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/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