On Tue, 2006-10-03 at 14:53 -0500, Steve French wrote: > What triggers flush/fsync of dirty pages on last (file) close of inode? Nothing. A close doesn't imply fsync. Dirty data is eventually written by pdflush, if something else (memory pressure, maybe) doesn't do it first. > I was hunting through the sys_close code and did not see a call > to fsync or filemap_write_and_wait there. Is it something done in libc > above the vfs? No > Someone had reported a problem with a writepages call coming in on with > no open files (so presumably the file was closed, with dirty pages not > written). This is normal behavior for most file systems. I thought cifs protected this by flushing dirty data in cifs_close. I don't think any data should be dirtied after cifs_close is called (on the last open file handle). -- David Kleikamp IBM Linux Technology Center - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
