Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!cornell!gvax!jqj
From: jqj@gvax.cs.cornell.edu (J Q Johnson)
Newsgroups: comp.unix.wizards
Subject: Re: Size of NFS "block"
Message-ID: <950@gvax.cs.cornell.edu>
Date: Fri, 31-Jul-87 14:50:37 EDT
Article-I.D.: gvax.950
Posted: Fri Jul 31 14:50:37 1987
Date-Received: Sun, 2-Aug-87 01:42:14 EDT
References: <931@gvax.UUCP> <8300008@iaoobelix.UUCP>
Reply-To: jqj@gvax.cs.cornell.edu (J Q Johnson)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 25

In article <8300008@iaoobelix.UUCP> woerz@iaoobelix.UUCP writes:
>> /***** iaoobelix:comp.unix.wiz / gvax!jqj /  9:27 pm  Jul 15, 1987*/
>> Note that varying block sizes is particularly a problem in an NFS environment.
>> When I do a "du", it reports sizes in blocks derived from a stat of the file
>> ...
>I looked at the manual of du on our suns and our VAX running vanilla
>4.2BSD, they state clearly that du reports the size in kilobytes.

Yes, but in fact they are wrong.  Both du versions use the "blocks" value
returned by stat(), and assume they know the size of a block.

On bullwinkle, a Gould 9080 running Gould OS 2.0.2 (almost pure 4.3BSD):
    bullwinkle-2% ls -l /fs/moose/mu/jqj/foo
    total 744
    -rwxr-xr-x  1 jqj        746054 Jul 31 14:41 vmunix
    bullwinkle-3% du /fs/moose/mu/jqj/foo
    745     /fs/moose/mu/jqj/foo
On ninib, a SUN-3/50 running SunOS 3.3:
    ninib-18% du /fs/moose/mu/jqj/foo
    373     /fs/moose/mu/jqj/foo
    ninib-19% df /fs/moose/mu/jqj/foo
    Filesystem            kbytes    used   avail capacity  Mounted on
    bullwinkle:/fs/moose/mu
			  222735  197881    2580    99%    /fs/moose/mu