Messages in this thread |  | | Date | Tue, 6 Feb 2001 11:51:15 -0600 (CST) | From | Josh Myer <> | Subject | Re: sync & asyck i/o |
| |
Hello,
On Tue, 6 Feb 2001, Alan Cox wrote:
[snip]
> In theory for a journalling file system it means the change is committed to the > log and the log to the media, and for other fs that the change is committed > to the final disk and recoverable by fsck worst case > > In practice some IDE disks do write merging and small amounts of write > caching in the drive firmware so you cannot trust it 100%. In addition some > higher end controllers will store to battery backed memory caches which is > normally just fine since the reboot will play through the ram cache. >
Does this imply that in order to ensure my data hits the drives, i should do a warm reboot and then shut down from the lilo: prompt or similiar?
apologies to bug you with a simple question, but i can see other people worrying about data loss here too.
-- /jbm
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |