From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Nils O. Selåsdal" <noselasd@frisurf.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: df on a nfs mounted share vs local?
Date: 05 Jul 2002 14:35:13 +0200 [thread overview]
Message-ID: <shsu1nel5dq.fsf@charged.uio.no> (raw)
In-Reply-To: <1025793209.10267.5.camel@space>
>>>>> " " == Nils O <Selåsdal <noselasd@frisurf.no>> writes:
> Just wondering, how come df reports root:~# df /mnt/export/
> Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda5
> 2562252 383792 2178460 15% /mnt/export on the server, while on
> a client that mounts /mnt/export over nfs: [root@space
> download]# df /mnt/nfs/ Filesystem 1k-blocks Used Available
> Use% Mounted on lfs:/mnt/export 2562256 383792 2178464 15%
> /mnt/nfs
> Just a few blocks diffrent, but I've seen much bigger.. also
> seen +/- a few % on "Use"
It is a rounding error. The block size on the NFS client is typically
4 or 8k, whereas the block size on the local filesystem is typically
512 bytes.
On most UNIX implementations, the 'statvfs()' call supports two
variables f_bsize and f_frsize, which allow you to distinguish between
the two. Linux lacks kernel support for the latter variable.
Cheers,
Trond
prev parent reply other threads:[~2002-07-05 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 14:35 df on a nfs mounted share vs local? Nils O. Selåsdal
2002-07-05 12:35 ` Trond Myklebust [this message]
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=shsu1nel5dq.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=noselasd@frisurf.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