linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Berthier, Emmanuel" <emmanuel.berthier@intel.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: fsync() does not flush all the file
Date: Thu, 1 Sep 2011 17:50:10 -0400	[thread overview]
Message-ID: <20110901215010.GA12057@infradead.org> (raw)
In-Reply-To: <65CD3FC07F3BF942ABE211646D72D77001C00C@IRSMSX102.ger.corp.intel.com>

On Thu, Sep 01, 2011 at 06:12:51PM +0000, Berthier, Emmanuel wrote:
> I've checked with traces that the issue is upper eMMC block driver.

What do you mean with this sentence?

Does your problem reproduce without eMMC in the game?  Does writing
directly to the block device and then fsync the data get it to disk?


  reply	other threads:[~2011-09-01 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 18:12 fsync() does not flush all the file Berthier, Emmanuel
2011-09-01 21:50 ` Christoph Hellwig [this message]
2011-09-02  7:59   ` Berthier, Emmanuel
2011-09-02  8:13     ` Christoph Hellwig
2011-09-02 10:53       ` Berthier, Emmanuel

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=20110901215010.GA12057@infradead.org \
    --to=hch@infradead.org \
    --cc=emmanuel.berthier@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).