From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ulrich Drepper <drepper@redhat.com>, Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: statfs() / statvfs() syscall ballsup...
Date: Thu, 9 Oct 2003 18:16:30 -0400 [thread overview]
Message-ID: <16261.56894.8109.858323@charged.uio.no> (raw)
Hi,
We appear to have a problem with the new statfs interface
in 2.6.0...
The problem is that as far as userland is concerned, 'struct statfs'
reports f_blocks, f_bfree,... in units of the "optimal transfer size":
f_bsize (backwards compatibility).
OTOH 'struct statvfs' reports the same values in units of the fragment
size (the blocksize of the underlying filesyste): f_frsize. (says
Single User Spec v2)
Both are apparently supposed to syscall down via sys_statfs()...
Question: how we're supposed to reconcile the two cases for something
like NFS, where these 2 values are supposed to differ?
Note that f_bsize is usually larger than f_frsize, hence conversions
from the former to the latter are subject to rounding errors...
Cheers,
Trond
next reply other threads:[~2003-10-09 22:16 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 22:16 Trond Myklebust [this message]
2003-10-09 22:26 ` statfs() / statvfs() syscall ballsup Linus Torvalds
2003-10-09 23:19 ` Ulrich Drepper
2003-10-10 0:22 ` viro
2003-10-10 4:49 ` Jamie Lokier
2003-10-10 5:26 ` Trond Myklebust
2003-10-10 12:37 ` Jamie Lokier
2003-10-10 13:46 ` Trond Myklebust
2003-10-10 14:35 ` Jamie Lokier
2003-10-10 15:32 ` Misc NFSv4 (was Re: statfs() / statvfs() syscall ballsup...) Trond Myklebust
2003-10-10 15:53 ` Jamie Lokier
2003-10-10 16:07 ` Trond Myklebust
2003-10-10 15:55 ` Michael Shuey
2003-10-10 16:20 ` Trond Myklebust
2003-10-10 16:45 ` J. Bruce Fields
2003-10-10 14:39 ` statfs() / statvfs() syscall ballsup Jamie Lokier
2003-10-09 23:31 ` Trond Myklebust
2003-10-10 12:27 ` Joel Becker
2003-10-10 14:59 ` Linus Torvalds
2003-10-10 15:27 ` Joel Becker
2003-10-10 16:00 ` Linus Torvalds
2003-10-10 16:26 ` Joel Becker
2003-10-10 16:50 ` Linus Torvalds
2003-10-10 17:33 ` Joel Becker
2003-10-10 17:51 ` Linus Torvalds
2003-10-10 18:13 ` Joel Becker
2003-10-10 16:27 ` Valdis.Kletnieks
2003-10-10 16:33 ` Chris Friesen
2003-10-10 17:04 ` Linus Torvalds
2003-10-10 17:07 ` Linus Torvalds
2003-10-10 17:21 ` Joel Becker
2003-10-10 16:01 ` Jamie Lokier
2003-10-10 16:33 ` Joel Becker
2003-10-10 16:58 ` Chris Friesen
2003-10-10 17:05 ` Trond Myklebust
2003-10-10 17:20 ` Joel Becker
2003-10-10 17:33 ` Chris Friesen
2003-10-10 17:40 ` Linus Torvalds
2003-10-10 17:54 ` Trond Myklebust
2003-10-10 18:05 ` Linus Torvalds
2003-10-10 20:40 ` Trond Myklebust
2003-10-10 21:09 ` Linus Torvalds
2003-10-10 22:17 ` Trond Myklebust
2003-10-11 2:53 ` Andrew Morton
2003-10-11 3:47 ` Trond Myklebust
2003-10-10 18:05 ` Joel Becker
2003-10-10 18:31 ` Andrea Arcangeli
2003-10-10 20:33 ` Helge Hafting
2003-10-10 20:07 ` Jamie Lokier
2003-10-12 15:31 ` Greg Stark
2003-10-12 16:13 ` Linus Torvalds
2003-10-12 22:09 ` Greg Stark
2003-10-13 8:45 ` Helge Hafting
2003-10-15 13:25 ` Ingo Oeser
2003-10-15 15:03 ` Greg Stark
2003-10-15 18:37 ` Helge Hafting
2003-10-16 10:29 ` Ingo Oeser
2003-10-16 14:02 ` Greg Stark
2003-10-21 11:47 ` Ingo Oeser
2003-10-10 18:20 ` Andrea Arcangeli
2003-10-10 18:36 ` Linus Torvalds
2003-10-10 19:03 ` Andrea Arcangeli
2003-10-09 23:16 ` Andreas Dilger
2003-10-09 23:24 ` Linus Torvalds
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=16261.56894.8109.858323@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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