From: Stan Hoeppner <stan@hardwarefreak.com>
To: Peter Grandi <pg@lxra2.to.sabi.co.UK>
Cc: Linux fs XFS <xfs@oss.sgi.com>
Subject: NOW:Peter goading Dave over delaylog - WAS: Re: raid10n2/xfs setup guidance on write-cache/barrier
Date: Fri, 16 Mar 2012 23:21:49 -0500 [thread overview]
Message-ID: <4F64115D.50208@hardwarefreak.com> (raw)
In-Reply-To: <20321.63389.586851.689070@tree.ty.sabi.co.UK>
On 3/15/2012 9:07 AM, Peter Grandi wrote:
>>>> I want to create a raid10,n2 using 3 1TB SATA drives.
>>>> I want to create an xfs filesystem on top of it. The
>>>> filesystem will be used as NFS/Samba storage.
>
> Consider also an 'o2' layout (it is probably the same thing for a
> 3 drive RAID10) or even a RAID5, as 3 drives and this usage seems
> one of the few cases where RAID5 may be plausible.
It's customary to note in your message body when you decide to CC
another mailing list, and why. I just got to my XFS folder and realized
you'd silently CC'd XFS. This was unnecessary and simply added noise to
XFS. Given some of your comments in this post I suspect you did so in
an effort to goad Dave into some kind of argument WRT delayed logging
performance, and his linux.conf.au presentation claims in general.
Doing this via subterfuge simply reduces people's level of respect for
you Peter.
If you want to have the delayed logging performance discussion/argument
with Dave, it should be its own thread on xfs@oss, not slipped into a
thread started on another list and CC'ed here. I'm removing linux-raid
from the CC list of this message, as anything further in this discussion
topic is only relevant to XFS.
I'm guessing either Dave chose not to take your bait, or simply didn't
read your message. If the former this thread will likely die now. If
the latter, and Dave decides to respond, I'm grabbing some popcorn, a
beer, and a lawn chair. ;)
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-17 4:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA8mOyDKrWg0QUEHxcD4ocXXD42nJu0TG+sXjC4j2RsigHTcmw@mail.gmail.com>
[not found] ` <4F61803A.60009@hardwarefreak.com>
[not found] ` <CAA8mOyCzs36YD_QUMq25HQf8zuq1=tmSTPjYdoFJwy2Oq9sLmw@mail.gmail.com>
2012-03-15 14:07 ` raid10n2/xfs setup guidance on write-cache/barrier Peter Grandi
2012-03-15 15:25 ` keld
2012-03-15 16:52 ` Jessie Evangelista
2012-03-15 17:15 ` keld
2012-03-15 17:40 ` keld
2012-03-15 16:18 ` Jessie Evangelista
2012-03-15 23:00 ` Peter Grandi
2012-03-16 3:36 ` Jessie Evangelista
2012-03-16 11:06 ` Michael Monnerie
2012-03-16 12:21 ` Peter Grandi
2012-03-16 17:15 ` Brian Candler
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-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 ` Stan Hoeppner [this message]
2012-03-17 22:34 ` NOW:Peter goading Dave over delaylog - WAS: " Dave Chinner
2012-03-18 2:09 ` Peter Grandi
2012-03-18 11:25 ` Peter Grandi
2012-03-18 14:00 ` Christoph Hellwig
2012-03-18 19:17 ` Peter Grandi
2012-03-19 9:07 ` Stan Hoeppner
2012-03-20 12:34 ` Jessie Evangelista
2012-03-18 18:08 ` Stan Hoeppner
2012-03-22 21:26 ` Peter Grandi
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
[not found] ` <4F633121.10800@hardwarefreak.com>
[not found] ` <CAKuK5J3GHgWcnYLqwRV8s_wMjO2nBVf7h=yONtn90kPn9A_3Gg@mail.gmail.com>
[not found] ` <CAKuK5J11JTdwZSBWj7DH7c+hE--MVNQVVrcKXaV2AO-wEpWBog@mail.gmail.com>
2012-03-16 19:28 ` raid10n2/xfs setup guidance on write-cache/barrier Peter Grandi
2012-03-17 0:02 ` Stan Hoeppner
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=4F64115D.50208@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox