| |||||||||||||
Turning off cachingTurning off cachingPosted Aug 9, 2013 4:17 UTC (Fri) by mathstuf (subscriber, #69389)In reply to: Turning off caching by sciurus Parent article: A survey of memory management patches
Would "-o remount,ro" work? Unmounting might be a little too disruptive. Of course, I'm not sure what happens when the filesystem behind a rw file I'm using gets remounted ro? Is it still writeable until I close it? Hit the next block? Delay the remount?
(Log in to post comments)
Turning off caching and switching to read-only Posted Aug 11, 2013 1:43 UTC (Sun) by giraffedata (subscriber, #1954) [Link] Switching a filesystem image read-only cleans the cache, but does not purge it. Thus, when you next read the file and see the correct data, that is no proof that the kernel correctly wrote to the device, which is what the OP wants. For that, you need to purge the cache and then read. As for what happens when you switch to read-only while writing to a file is in progress: The mount() system call to switch to read-only fails. It fails if any file is open for writing. And I'll tell you when else it fails, which causes no end of pain: when there's an unlinked file (a file not in any directory) in the filesystem. Because the kernel must update the filesystem when the file eventually closes (because it must delete the file at that time), the kernel cannot allow the switch to r/o.
|
|||||||||||||