Corruption caused by umount not flushing the buffer cache.

[Richard B. Johnson]

On Tue, 25 Jan 2000, Alan Cox wrote:

> > It is not as you say "my caches flushing". It is "our caches flushing".
> > Unmounting a file-system must force all pending I/O operations to the
> > mounted device to complete.
> 
> He's talking about reads not writes.
> 
> > You cannot make changes in the behavior of a Linux, that divorce it
> > completely from the Historical behavior of Unix.
> 
> I can't find anything  in the posix or SuS about this. In fact I can't find
> anything in the V7 manual about it either.
> 
> Its quite valid for non-removable media to keep the data cached
> 

Is a ram-disk or NFS or 'loop' "non-removable". I think not. The
next time you try to build a RedHat distribution using the current
Ram-Disk or loop, you will understand. These problems were caused
by removing the calls that used to unvalidate buffers. They are
not 'policy' as you previously stated.

Cheers,
Dick Johnson

Penguin : Linux version 2.3.39 on an i686 machine (800.63 BogoMips).


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo en vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/