public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfltc@us.ibm.com>
To: linux-fsdevel@vger.kernel.org
Cc: Shirish S Pargaonkar <shirishp@us.ibm.com>
Subject: What trigge fsync of file on last close of the open inode?
Date: Tue, 03 Oct 2006 14:53:12 -0500	[thread overview]
Message-ID: <4522BFA8.9040000@us.ibm.com> (raw)

What triggers flush/fsync of dirty pages on last (file) close of inode?  
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?

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).

             reply	other threads:[~2006-10-03 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 19:53 Steve French [this message]
2006-10-03 20:05 ` What trigge fsync of file on last close of the open inode? Dave Kleikamp
2006-10-03 20:45   ` Steve French
2006-10-03 21:15     ` Zach Brown
2006-10-03 21:40       ` Dave Kleikamp
2006-10-03 23:43         ` Zach Brown
2006-10-04 15:13       ` Steve French
2006-10-03 23:13     ` Jeremy Allison
2006-10-04 20:46       ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4522BFA8.9040000@us.ibm.com \
    --to=smfltc@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=shirishp@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox