Messages in this thread | | | Date | Thu, 23 Jul 1998 08:01:27 +0200 (CEST) | From | Rik van Riel <> | Subject | Re: 2.1.110 freepages.min change -- disk coruption |
| |
On Thu, 23 Jul 1998, Trever Adams wrote:
> My questions are simple: If the inode/file/whatever that the dcache > entry referred to is still open and being used, or hasn't yet been > synched to disk and is "closed" and that dcache entry is pruned, > does/can it cause disk corruption or data corruption in the file. Q.
Currently we do COW to the buffer cache when writing to a file. The buffer cache is _disk_ indexed and the page cache is inode indexed. When pruning the inode cache, this has no influence whatsoever on the disk cache (containing the dirty blocks).
> #2, Could the disk corruption that a few people have reported be caused > by the bad patch to vmalloc (at least I believe that was the malloc > involved)?
Disk corruption is often caused by memory scribblings so you should consider every memory change suspect.
It must be something subtle or something else however, as the new vmalloc code looks good to me...
Rik. +-------------------------------------------------------------------+ | Linux memory management tour guide. H.H.vanRiel@phys.uu.nl | | Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ | +-------------------------------------------------------------------+
- 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.altern.org/andrebalsa/doc/lkml-faq.html
| |