Re: df - bugs?

[Bob Proulx]

> Try on this:
> 
> 1. mount /mnt/floppy
> 2. cp file /mnt/floppy (file )
> 3. umount /mnt/floppy (write on floppy is working on back)
> 4. df (on other console)
> 
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/hda2              2071416   1888584     77608  96% /
> /dev/hda6              3099260   1656596   1285232  56% /var
> /dev/hda3              1035692    225236    757844  23% /home
> /dev/hda7              1881652   1715192     70876  96% /mnt/disk2
> /dev/hdb3              3075536        20   2919284   0% /mnt/hdb3
> /dev/fd0               2071416   1888584     77608  96% /mnt/floppy
>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> It is OK? ;-)
> Floppy has 2GB :-)

An interesting case!

> address@hidden /root]# df --version
> df (GNU fileutils) 4.0p
> 
> kernel 2.4.5

I would guess this is a kernel issue and not a df issue.  Generally
commands like df just report what they are told by the kernel.

However, it is also possible that the unmount happens at a time when
df is not expecting the disk to have gone away.  Perhaps the code
just checked that it was there, and then performed another operation
thinking that it did not need to check again, and got caught in a
condition that was not consistently error checked.

Thanks for the report.

Bob