public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Jens Axboe <axboe@suse.de>, linux-kernel <linux-kernel@vger.kernel.org>
Cc: Arjan van de Ven <arjan@infradead.org>
Subject: Re: Getting 'sync' to flush disk cache?
Date: Mon, 14 Aug 2006 17:09:07 -0600	[thread overview]
Message-ID: <44E10293.7000508@shaw.ca> (raw)
In-Reply-To: <fa.PWNfC1odploxRBgLE1vdR69UF9s@ifi.uio.no>

Jens Axboe wrote:
> On Mon, Aug 14 2006, Arjan van de Ven wrote:
>> On Mon, 2006-08-14 at 14:39 -0400, Jeff Garzik wrote:
>>> So...  has anybody given any thought to enabling fsync(2), fdatasync(2), 
>>> and sync_file_range(2) issuing a [FLUSH|SYNCHRONIZE] CACHE command?
>>>
>>> This has bugged me for _years_, that Linux does not do this.  Looking at 
>>> forums on the web, it bugs a lot of other people too.
>> eh afaik 2.6.17 and such do this if you have barriers enabled...
> 
> That is correct, but it only works on reiserfs and XFS and user space
> really cannot tell whether it did the right thing or not. File system
> developers really should take this more seriously...
> 

I was under the impression that this just worked under recent kernels. 
I'm disappointed to hear that it doesn't. It always annoys me that 
issues like this sometimes just seem to stick around forever in the 
kernel without getting the attention they should (and tend not to be 
well documented either..)

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-08-14 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.W0uMWcngieRXsM23OSdM5c2wdZI@ifi.uio.no>
     [not found] ` <fa.qZ/OWlxPTq6xK9TZx+9e39itX9k@ifi.uio.no>
     [not found]   ` <fa.PWNfC1odploxRBgLE1vdR69UF9s@ifi.uio.no>
2006-08-14 23:09     ` Robert Hancock [this message]
2006-08-15  5:45       ` Getting 'sync' to flush disk cache? Jens Axboe
2006-08-14 18:39 Jeff Garzik
2006-08-14 19:34 ` Arjan van de Ven
2006-08-14 20:15   ` Jens Axboe
2006-08-14 21:04     ` Jeff Garzik

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=44E10293.7000508@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=arjan@infradead.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@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