From: wind@cocodriloo.com
To: Doug McNaught <doug@mcnaught.org>
Cc: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4 has O_SYNC bug ?
Date: Sat, 22 Mar 2003 22:05:35 +0100 [thread overview]
Message-ID: <20030322210535.GD891@wind.cocodriloo.com> (raw)
In-Reply-To: <m37kar42ge.fsf@varsoon.wireboard.com>
On Sat, Mar 22, 2003 at 02:37:53PM -0500, Doug McNaught wrote:
> Rob van Nieuwkerk <robn@verdi.et.tudelft.nl> writes:
>
> > But the strange thing is this: always after 30s the kernel performs
> > extra writes to the CF. It seems it's flushing some kind of dirty buffer
> > from the buffer cache. But there is not supposed to be any dirty buffer:
> > all data should have been written already to the CF because the partition
> > was opened with O_SYNC !
>
> noatime?
>
> -Doug
As he stated he was using no filesystem, but a treating the partition as
a raw file, I suppose it can't be atime-refreshing... perhaps using
O_DIRECT will solve it?
Greets, Antonio.
[sorry for double response Doug, I forgot to reply to list earlier]
prev parent reply other threads:[~2003-03-22 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 14:48 2.4 has O_SYNC bug ? Rob van Nieuwkerk
2003-03-22 19:37 ` Doug McNaught
2003-03-22 20:05 ` Rob van Nieuwkerk
2003-03-22 21:05 ` wind [this message]
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=20030322210535.GD891@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=doug@mcnaught.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robn@verdi.et.tudelft.nl \
/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