public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	Subranshu Patel <spatel.ml@gmail.com>,
	xfs@oss.sgi.com
Subject: Re: Xfs_repair and journalling  --  EXT4 journal replay discussion
Date: Sun, 31 Mar 2013 13:03:04 +1100	[thread overview]
Message-ID: <20130331020304.GL6369@dastard> (raw)
In-Reply-To: <51573461.8070006@hardwarefreak.com>

On Sat, Mar 30, 2013 at 01:52:17PM -0500, Stan Hoeppner wrote:
> On 3/30/2013 12:40 PM, Eric Sandeen wrote:
> > On 3/30/13 7:49 AM, Stan Hoeppner wrote:
> 
> >> Ok, so here's the skinny on the source of our confusion WRT how/when
> >> EXT4 replays journals, and it's rather interesting.  Ted Ts'o explained
> >> the following.
> > 
> > Where was this, out of curiosity?
> 
> Private email exchange with Ted.  I thought it was best from an
> etiquette standpoint not to wholesale paste his two private emails to
> the XFS list, but to summarize.  Maybe it would be ok if I put it on my
> web server for a couple of days then remove it.
> 
> http://www.hardwarefreak.com/ext4-journaling.txt

That again?  I'll just point to this post from Ted in 2004:

http://zork.net/~nick/mail/why-reiserfs-is-teh-sukc

It's the same FUD about XFS journalling and power failures that Ted
has been claiming for the past 10+ years. It's been rebutted so many
times I can now do it in three words: volatile drive caches.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-03-31  2:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 15:56 Xfs_repair and journalling Subranshu Patel
2013-03-17  2:22 ` Stan Hoeppner
2013-03-17  3:01 ` Michael L. Semon
2013-03-17  5:26 ` Stan Hoeppner
2013-03-17 11:42   ` Subranshu Patel
2013-03-17 14:50     ` Stan Hoeppner
2013-03-17 15:18     ` Matthias Schniedermeyer
2013-03-17 23:20     ` Dave Chinner
2013-03-18 18:22     ` Ben Myers
2013-03-18 20:58       ` Martin Steigerwald
2013-03-18 20:50     ` Martin Steigerwald
2013-03-19  4:02     ` Eric Sandeen
2013-03-19  6:19       ` Stan Hoeppner
2013-03-19  8:24         ` Martin Steigerwald
2013-03-19 10:14           ` Stan Hoeppner
2013-03-30 12:49             ` Xfs_repair and journalling -- EXT4 journal replay discussion Stan Hoeppner
2013-03-30 17:40               ` Eric Sandeen
2013-03-30 18:52                 ` Stan Hoeppner
2013-03-30 20:21                   ` Eric Sandeen
2013-03-31 11:24                     ` Stan Hoeppner
2013-03-31  2:03                   ` Dave Chinner [this message]
2013-03-31  1:35               ` Dave Chinner
2013-03-18 20:37   ` Xfs_repair and journalling Martin Steigerwald

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=20130331020304.GL6369@dastard \
    --to=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --cc=spatel.ml@gmail.com \
    --cc=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.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