From: Stan Hoeppner <stan@hardwarefreak.com>
To: Peter Grandi <pg@lxra2.to.sabi.co.UK>
Cc: Linux RAID <linux-raid@vger.kernel.org>, Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: raid10n2/xfs setup guidance on write-cache/barrier
Date: Fri, 23 Mar 2012 00:10:25 -0500 [thread overview]
Message-ID: <4F6C05C1.4020204@hardwarefreak.com> (raw)
In-Reply-To: <20331.39194.377610.888636@tree.ty.sabi.co.UK>
On 3/22/2012 4:26 PM, Peter Grandi wrote:
[snipped 2-3 pages of redundant nonsense, linked docs, and filesystem
concepts everyone is already familiar with]
> Overselling 'delaylog' with cheeky propaganda glossing over the
> heavy tradeoffs involved is understandable, but quite wrong.
And now we come full circle to what started this mess of a discussion:
Peter's dislike of Dave's presentation of delaylog, and XFS in general,
at linux.conf.au.
Peter, if *you* had been giving Dave's presentation at linux.conf.au,
how would *you* have presented delayed logging differently? How much
time would you have spent warning of the dangers of potential data loss
upon a crash and how would you have presented it? Note I'm not asking
you to re-critique Dave's presentation. I'm asking you to write your
own short presentation of the delayed logging feature, so we can all see
it done the right way, without "cheeky propaganda" and without "glossing
over the heavy tradeoffs".
We're all on the edge of our seats, eagerly awaiting your expert XFS
presentation Peter.
--
Stan
WARNING: multiple messages have this Message-ID (diff)
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Peter Grandi <pg@lxra2.to.sabi.co.UK>
Cc: Linux RAID <linux-raid@vger.kernel.org>, Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: raid10n2/xfs setup guidance on write-cache/barrier
Date: Fri, 23 Mar 2012 00:10:25 -0500 [thread overview]
Message-ID: <4F6C05C1.4020204@hardwarefreak.com> (raw)
In-Reply-To: <20331.39194.377610.888636@tree.ty.sabi.co.UK>
On 3/22/2012 4:26 PM, Peter Grandi wrote:
[snipped 2-3 pages of redundant nonsense, linked docs, and filesystem
concepts everyone is already familiar with]
> Overselling 'delaylog' with cheeky propaganda glossing over the
> heavy tradeoffs involved is understandable, but quite wrong.
And now we come full circle to what started this mess of a discussion:
Peter's dislike of Dave's presentation of delaylog, and XFS in general,
at linux.conf.au.
Peter, if *you* had been giving Dave's presentation at linux.conf.au,
how would *you* have presented delayed logging differently? How much
time would you have spent warning of the dangers of potential data loss
upon a crash and how would you have presented it? Note I'm not asking
you to re-critique Dave's presentation. I'm asking you to write your
own short presentation of the delayed logging feature, so we can all see
it done the right way, without "cheeky propaganda" and without "glossing
over the heavy tradeoffs".
We're all on the edge of our seats, eagerly awaiting your expert XFS
presentation Peter.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-23 5:10 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 0:30 raid10n2/xfs setup guidance on write-cache/barrier Jessie Evangelista
2012-03-15 5:38 ` Stan Hoeppner
2012-03-15 12:06 ` Jessie Evangelista
2012-03-15 14:07 ` Peter Grandi
2012-03-15 14:07 ` Peter Grandi
2012-03-15 15:25 ` keld
2012-03-15 15:25 ` keld
2012-03-15 16:52 ` Jessie Evangelista
2012-03-15 16:52 ` Jessie Evangelista
2012-03-15 17:15 ` keld
2012-03-15 17:15 ` keld
2012-03-15 17:40 ` keld
2012-03-15 17:40 ` keld
2012-03-15 16:18 ` Jessie Evangelista
2012-03-15 16:18 ` Jessie Evangelista
2012-03-15 23:00 ` Peter Grandi
2012-03-15 23:00 ` Peter Grandi
2012-03-16 3:36 ` Jessie Evangelista
2012-03-16 3:36 ` Jessie Evangelista
2012-03-16 11:06 ` Michael Monnerie
2012-03-16 11:06 ` Michael Monnerie
2012-03-16 12:21 ` Peter Grandi
2012-03-16 12:21 ` Peter Grandi
2012-03-16 17:15 ` Brian Candler
2012-03-16 17:15 ` Brian Candler
2012-03-17 15:35 ` Peter Grandi
2012-03-17 15:35 ` Peter Grandi
2012-03-17 21:39 ` raid10n2/xfs setup guidance on write-cache/barrier (GiB alignment) Zdenek Kaspar
2012-03-17 21:39 ` Zdenek Kaspar
2012-03-18 0:08 ` Peter Grandi
2012-03-18 0:08 ` Peter Grandi
2012-03-26 19:50 ` raid10n2/xfs setup guidance on write-cache/barrier Martin Steigerwald
2012-03-17 4:21 ` NOW:Peter goading Dave over delaylog - WAS: " Stan Hoeppner
2012-03-17 22:34 ` Dave Chinner
2012-03-18 2:09 ` Peter Grandi
2012-03-18 2:09 ` Peter Grandi
2012-03-18 11:25 ` Peter Grandi
2012-03-18 11:25 ` Peter Grandi
2012-03-18 14:00 ` Christoph Hellwig
2012-03-18 14:00 ` Christoph Hellwig
2012-03-18 19:17 ` Peter Grandi
2012-03-18 19:17 ` Peter Grandi
2012-03-19 9:07 ` Stan Hoeppner
2012-03-19 9:07 ` Stan Hoeppner
2012-03-20 12:34 ` Jessie Evangelista
2012-03-20 12:34 ` Jessie Evangelista
2012-03-18 18:08 ` Stan Hoeppner
2012-03-18 18:08 ` Stan Hoeppner
2012-03-22 21:26 ` Peter Grandi
2012-03-22 21:26 ` Peter Grandi
2012-03-23 5:10 ` Stan Hoeppner [this message]
2012-03-23 5:10 ` Stan Hoeppner
2012-03-23 22:48 ` Martin Steigerwald
2012-03-24 1:27 ` Peter Grandi
2012-03-24 16:27 ` GNU 'tar', Schilling's 'tar', write-cache/barrier Peter Grandi
2012-03-24 17:11 ` Brian Candler
2012-03-24 18:35 ` Peter Grandi
2012-03-16 12:25 ` raid10n2/xfs setup guidance on write-cache/barrier Stan Hoeppner
2012-03-16 18:01 ` Jon Nelson
2012-03-16 18:03 ` Jon Nelson
2012-03-16 19:28 ` Peter Grandi
2012-03-16 19:28 ` Peter Grandi
2012-03-17 0:02 ` Stan Hoeppner
2012-03-17 0:02 ` Stan Hoeppner
2012-03-17 22:10 ` Zdenek Kaspar
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=4F6C05C1.4020204@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=pg@lxra2.to.sabi.co.UK \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.