From: "Stephen C. Tweedie" <sct@redhat.com>
To: John Bradford <john@grabjohn.com>
Cc: Andrew Morton <akpm@digeo.com>,
joe.korty@ccur.com, Andreas Dilger <adilger@clusterfs.com>,
rusty@rustcorp.com.au, riel@conectiva.com.br,
linux-kernel@vger.kernel.org, hch@sgi.com,
Stephen Tweedie <sct@redhat.com>
Subject: Re: 2.4.21-pre2 stalls out when running unixbench
Date: 06 Jan 2003 13:20:35 +0000 [thread overview]
Message-ID: <1041859235.2690.48.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <200301061215.h06CFheY001499@darkstar.example.net>
Hi,
On Mon, 2003-01-06 at 12:15, John Bradford wrote:
> What!? I'm suprised that no userspace applications were broken by
> sync returning before the data is safely on oxide, even though it
> doesn't violate the POSIX spec.
sync(2) syncs _everything_ --- every M/O or floppy disk, every
filesystem no matter if it's fat or native Unix. It's way too
heavyweight for most applications which have synchronisation
requirements, when fsync() or O_SYNC are much more precise.
I think I can recall one or two mutterings about people worried about
theoretical risks of doing things like "lilo; sync; reboot", but that's
a different class of risk altogether. (It's complicated by the problem
that after a sync, ext3 guarantees that the data and metadata is on
disk, but it may still be in the journal, so lilo won't necessarily see
the right stuff with sync() alone --- ext3 plays extra tricks when it
sees bmap to try to solve this.)
--Stephen
next prev parent reply other threads:[~2003-01-06 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 16:56 Joe Korty
2003-01-03 20:07 ` Andrew Morton
2003-01-03 20:30 ` Andrew Morton
2003-01-04 1:11 ` Joe Korty
2003-01-04 11:11 ` Andrew Morton
2003-01-05 2:58 ` Joe Korty
2003-01-06 12:10 ` Stephen C. Tweedie
2003-01-06 12:15 ` John Bradford
2003-01-06 13:20 ` Stephen C. Tweedie [this message]
2003-01-06 12:16 ` Andrew Morton
2003-01-06 13:23 ` Stephen C. Tweedie
2003-01-11 8:10 ` Christoph Hellwig
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=1041859235.2690.48.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=hch@sgi.com \
--cc=joe.korty@ccur.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®