Message-ID: <01bb01c2322f$c1591e10$1e210a0a@spi.co.za>
From: "Allen Van Der Ross" <allen@ct.spi.co.za>
To: <clug-tech@clug.org.za>
References: <010701c23190$d8b69050$1e210a0a@spi.co.za> <20020723095452.C1055@crystal.2d3d.co.za> <018b01c23226$3dd265a0$1e210a0a@spi.co.za> <20020723113918.B2674@crystal.2d3d.co.za>
Subject: Re: [CLUG-tech] statfs()  vs. df
Organization: SPI
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: clug-tech-admin@clug.org.za
Errors-To: clug-tech-admin@clug.org.za
Precedence: bulk
Reply-To: clug-tech@clug.org.za
Date: Tue, 23 Jul 2002 12:00:16 +0200

> allen@eagle:~$ uname -a
> Linux eagle.spi.co.za 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown

I just had a look at the source for the df from fileutils 4.0.37 and it can
get the filesystem stats in a number of ways

1. statfs()
2. reading a filsys structure directly from the superblock of the
filesystem.
3. statvfs()

I've modified my test program to display both. See if you get different
output. Also try compiling the program with -D_LARGEFILE64_SOURCE and see if
that makes a difference (shouldn't since your partition is quite small).

<
< I have also played with options 1 and 3, using statfs() and statvfs()
which
< both display the same information.
< Compiling t.c with -D_LARGEFILE64_SOURCE doesn't make a differance
< as you thought. I was hoping not to get involved with option 2 for now,
< since time does not permit and I'm on the verge of execing("df -k").

(Which reminds me. How big is your partition really? I take it df gave the
correct output which makes it a 2.8G partition?)

< Yep, its quite small. I have to re-install this machine this weekend and
that's
< one of the things I need to fix. :)

Also, what filesystem do you have on there?

< ext2fs is all I use on this machine.

If this is the same I give up. In that case I suggest you grab a copy of the
latest fileutils, compile it with debugging and run df through the debugger.
(break on get_fs_usage and step through the function to see what method it
uses on your system).

< yes it is the same. I will check out fileutils.
< yet I saw something very interesting...hmmm....
< don't understand it, but all the programs (we) wrote
< did return valid values, but for / (root) partition, which
< is on /dev/hda8 (even tho I explicitly tested with /dev/hda9)
< see this:

gcc t.c  (your latest t.c)
allen@eagle:~$ ./a.out
f_blocks: 350021, f_bsize: 1024
f_bsize: 1024, f_blocks: 350021

allen@eagle:~$ ./fs /dev/hda
/dev/hda:       total blocks 350021     free blocks 217464

allen@eagle:~$ ./fs /dev/hda9
/dev/hda9:      total blocks 350021     free blocks 217458

allen@eagle:~$ df -k
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda8               350021    132578    199372  40% /
/dev/hda9              3028080   2575624    298636  90% /usr
...

What can you make of it?

-Allen


-- 
Clug-tech mailing list
Clug-tech@clug.org.za
To (un)subscribe:
http://www2.clug.org.za/mailman/listinfo/clug-tech