[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: df output (fwd)
> ---------- Forwarded message ----------
> Date: Mon, 11 May 1998 11:09:46 +0000
> From: johnnie ligotage <johnnie@ligotage.demon.co.uk>
> To: MiNT Enquiries <mint@atari.archive.umich.edu>
> Subject: df output
>
> Hi MiNT-ers
>
> Can anyone explain the following, and suggest the cause and possibly a
> solution :)
>
> My hard drive is partitioned as follows:
>
> c: - 52.54 Mb TOS boot partition
> d: - 63.02 Mb TOS applications
> e: - 157.40 Mb TOS "anything-goes" partition
> f: - 63.02 Mb MINIX KGMD root partition
> g: - 21.07 Mb MINIX /home - sln'd in mint.cnf
> h: - 21.07 Mb MINIX /var/spool/mail - mounted
> during boot
> i: - 88.99 Mb MINIX /usr/local - mounted
> during boot
> j: - 73.50 Mb MINIX /usr/local/csound -
> mounted during boot
>
> I also have a zip on k:
>
> All minix partitions have a maximum filename length of 64; I'm using
> HDDriver v6; oh yeah! - I have a falcon AND the results do not differ
> between 1.12.* and 1.14.7 which I'm running mint030 renamed to mintnp.
>
> when I execute `df` from $HOME I get this...
>
> Filesystem 1024-blocks Used Available Capacity Mounted on
> a: 711 611 100 86% /a
> c: 51200 30804 20396 60% /c
> d: 61422 45086 16336 73% /d
> e: 153616 116008 37608 76% /e
> f: 60249 45345 14904 75% /j
> g: 20150 17875 2275 89% /g
> h: 60249 45345 14904 75% h:/
> i: 60249 45345 14904 75% i:/
> j: 60249 45345 14904 75% j:/
> k: 98224 79464 18760 81% /k
> u: 20150 17875 2275 89% u:/
> pipefs: 11672 56 11616 0% /pipe
> procfs: 13930 2311 11619 17% /proc
> shmfs: 13930 2311 11619 17% /shm
>
> Why are drives h:, i: & j: reported with the same figures as f:, and why
This is because when you minixfs-mount h: on f:/var/spool/mail, accesses
to h: itself are routed to f:/. As MiNT does not have a concept of
mounting file systems anywhere except on u:/, no tool can determine
the "true" Minix FS mount point.
> is f: reportedly mounted on /j? And check out the figures for u: - they
> are the same as for g:...
Well. Blame your df version. My df.ttp certainly reports the correct
value (http://www.muenster.de/~reschke/soft_e.html).
> If I do the same from /, ie the root of the filesystem, I get...
>
> Filesystem 1024-blocks Used Available Capacity Mounted on
> a: 711 611 100 86% /a
> c: 51200 30804 20396 60% /c
> d: 61422 45086 16336 73% /d
> e: 153616 116008 37608 76% /e
> f: 60249 45345 14904 75% /j
> g: 20150 17876 2274 89% /g
> h: 60249 45345 14904 75% h:/
> i: 60249 45345 14904 75% i:/
> j: 60249 45345 14904 75% j:/
> k: 98224 79464 18760 81% /k
> pipefs: 11672 56 11616 0% /pipe
> procfs: 13930 2311 11619 17% /proc
> shmfs: 13930 2311 11619 17% /shm
>
> exactly the same - ignoring the fact that g: differs by a block, but where
> has u: gone...?!!
>
> Intestingly enough, I hace just `cd /usr/local;df` (i:) and `cd
> /usr/local/csound;df` (j:) AND `cd /var/spool/mail;df` (h:) and each time
> the figures for u: _probably_ indicated the space left on that mount-point
> - _probably_, as I can't say for certain...
>
> Is this a feature, a bug or am I doing something wrong?
>
> Just for completeness, here's my /etc/fstab...
>
> f / minix - - -
> g /home minix - - -
> h /var/spool/mail minix - - -
> i /usr/local minix - - -
> j /usr/local/csound minix - - -
Is the df you are using actually *using* /etc/fstab? As I have said
before, the concept of a static fstab doesn't translate very well
to MiNT because the type of filesystem can change with every media
change...
Regards, jr