From: engler@csl.stanford.edu (Dawson Engler)
To: sfaibish@emc.com (sfaibish)
Cc: shaggy@linux.vnet.ibm.com (Dave Kleikamp),
tytso@mit.edu (Theodore Tso),
val_henson@linux.intel.com (Valerie Henson),
linux-fsdevel@vger.kernel.org, csar@stanford.edu (Can Sar),
junfeng@gmail.com (Junfeng Yang)
Subject: Re: Fix(es) for ext2 fsync bug
Date: Thu, 15 Feb 2007 10:54:11 -0800 (PST) [thread overview]
Message-ID: <20070215185412.455311810F7D0@csl.stanford.edu> (raw)
In-Reply-To: <op.tnsr13qnunckof@usensfaibisl2e.eng.emc.com> from "sfaibish" at Feb 15, 2007 10:59:53 AM
> It was my understanding from the persentation of Dawson that ext3 and jfs
> have
> same problem. It is not an ext2 only problem. Also whatever solution we
> adopt
> we need to be sure that we test it using the eXplode methodology.
apologies for dropping in randomly into the discussion: if this is
about the crash-during-recovery bugs, the specific ones i discussed
have been fixed in jfs and ext3 (junfeng: this is correct, right?).
i should have made this clear in the talk (along with many other things:
grabbing junfeng's slides and blathering about them w/o preperation is
not the right algorithm for giving a good talk.)
the other error --- fsync of file data on ext2 that reuses a freed inode
from a file that was not flushed to disk ---- is still open.
next prev parent reply other threads:[~2007-02-15 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 19:54 Fix(es) for ext2 fsync bug Valerie Henson
2007-02-14 20:31 ` David Chinner
2007-02-14 21:26 ` Dave Kleikamp
2007-02-14 23:32 ` David Chinner
2007-02-14 21:08 ` sfaibish
2007-02-15 14:20 ` Theodore Tso
2007-02-15 15:09 ` Dave Kleikamp
2007-02-15 15:59 ` sfaibish
2007-02-15 16:39 ` Dave Kleikamp
2007-02-15 17:15 ` Theodore Tso
2007-02-15 17:52 ` sfaibish
[not found] ` <21e789ec0702151111v4cb2aa8dqa168c886cb909c9@mail.gmail.com>
2007-02-15 19:26 ` Dave Kleikamp
2007-02-15 18:54 ` Dawson Engler [this message]
[not found] ` <21e789ec0702151118x1c6af801gd34981d72db0f5b2@mail.gmail.com>
[not found] ` <21e789ec0702151128x744f61e5lb24d2da972af185a@mail.gmail.com>
2007-02-16 1:18 ` Theodore Tso
2007-02-20 21:13 ` Valerie Henson
[not found] ` <21e789ec0702201330x1c2706b7kcd055b97cb37e0e@mail.gmail.com>
2007-02-20 21:39 ` Valerie Henson
2007-02-20 21:47 ` Dawson Engler
2007-02-20 22:25 ` Dave Kleikamp
2007-02-20 21:30 ` Valerie Henson
2007-02-20 22:12 ` Erez Zadok
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=20070215185412.455311810F7D0@csl.stanford.edu \
--to=engler@csl.stanford.edu \
--cc=csar@stanford.edu \
--cc=junfeng@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfaibish@emc.com \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
--cc=val_henson@linux.intel.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).