From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Bryan Henderson <hbryan@us.ibm.com>, Al Boldi <a1426z@gawab.com>,
linux-fsdevel@vger.kernel.org, linux-xfs@oss.sgi.com,
Steve Lord <lord@xfs.org>, 'Nathan Scott' <nathans@sgi.com>,
reiserfs-list@namesys.com
Subject: Re: XFS corruption during power-blackout
Date: Thu, 30 Jun 2005 21:44:37 +0200 [thread overview]
Message-ID: <20050630194437.GC8374@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <054069.b93858d6b97c07747dc32be2dd8981b254d981528781006053dce7be58de88865a43b162.IBX@taniwha.stupidest.org>
On Thu, 30 June 2005 11:46:27 -0700, Chris Wedgwood wrote:
> On Thu, Jun 30, 2005 at 12:30:20PM -0400, Bryan Henderson wrote:
>
> > In others, it implements "everything that was buffered when sync()
> > started is hardened before the next sync() returns,"
>
> That is what happens now. I'm not sure any other behavior makes sense
> does it?
>
> If it happens differently I would call that a bug.
While I agree with all the rest, this part confuses me. Do you mean
that sync() should altually return immediatly, but the second sync()
block until all data present at the time of the previous sync() is
hardened?
Or do you rather mean that a single sync() should block until all data
currently present is hardened?
Jörn
--
It is better to die of hunger having lived without grief and fear,
than to live with a troubled spirit amid abundance.
-- Epictetus
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-06-30 19:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050629001847.GB850@frodo>
2005-06-29 4:53 ` XFS corruption during power-blackout Al Boldi
2005-06-29 16:38 ` Christian Rice
2005-06-29 17:02 ` Chris Wedgwood
2005-06-29 17:56 ` Steve Lord
2005-06-29 20:56 ` Chris Wedgwood
2005-06-30 16:30 ` Bryan Henderson
2005-06-30 18:46 ` Chris Wedgwood
2005-06-30 19:44 ` Jörn Engel [this message]
2005-06-30 20:32 ` Chris Wedgwood
2005-06-30 21:07 ` Jörn Engel
2005-07-01 12:36 ` Ric Wheeler
2005-07-01 12:56 ` Jens Axboe
2005-06-30 20:49 ` Bryan Henderson
2005-07-01 12:53 ` Ric Wheeler
2005-07-01 18:24 ` Bryan Henderson
2005-07-01 19:58 ` David Masover
2005-07-01 21:10 ` Jörn Engel
2005-07-01 21:39 ` David Masover
2005-07-01 1:09 ` Stewart Smith
2005-07-05 15:53 ` Sonny Rao
2005-06-29 21:10 ` Nathan Scott
2005-07-01 8:17 ` David Masover
2005-07-01 9:24 ` Jens Axboe
[not found] ` <20050701131950.GA15180@ime.usp.br>
2005-07-01 13:57 ` Ric Wheeler
2005-07-01 18:37 ` Bryan Henderson
2005-07-01 18:41 ` Jens Axboe
2005-07-11 12:53 ` Ric Wheeler
2005-07-01 14:05 ` Al Boldi
2005-07-01 16:35 ` Alistair John Strachan
2005-07-05 15:49 ` Sonny Rao
2005-07-05 17:25 ` Al Boldi
2005-07-05 18:10 ` Sonny Rao
2005-07-05 19:24 ` Dieter Nützel
2005-07-06 4:24 ` Al Boldi
2005-07-06 4:46 ` Nathan Scott
2005-07-16 7:02 Al Boldi
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=20050630194437.GC8374@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=a1426z@gawab.com \
--cc=cw@f00f.org \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@xfs.org \
--cc=nathans@sgi.com \
--cc=reiserfs-list@namesys.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;
as well as URLs for NNTP newsgroup(s).