Linux-kernel mailing list archive 2000-04,: Re: Corruption caused by umount not flushing the buffer cache.

# Re: Corruption caused by umount not flushing the buffer cache.

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 25 Jan 2000 14:52:14 +0000 (GMT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Andries.Brouwer@cwi.nl: "[PATCH] kill sys_tz.tz_dsttime"
- Previous message: Richard B. Johnson: "Re: Corruption caused by umount not flushing the buffer cache."
- Next in thread: Richard B. Johnson: "Re: Corruption caused by umount not flushing the buffer cache."
- Reply: Richard B. Johnson: "Re: Corruption caused by umount not flushing the buffer cache."
- Reply: Guest section DW: "Re: Corruption caused by umount not flushing the buffer cache."

> 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

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

- Next message: Andries.Brouwer@cwi.nl: "[PATCH] kill sys_tz.tz_dsttime"
- Previous message: Richard B. Johnson: "Re: Corruption caused by umount not flushing the buffer cache."
- Next in thread: Richard B. Johnson: "Re: Corruption caused by umount not flushing the buffer cache."
- Reply: Richard B. Johnson: "Re: Corruption caused by umount not flushing the buffer cache."
- Reply: Guest section DW: "Re: Corruption caused by umount not flushing the buffer cache."