From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Jessie Evangelista <jessie.evangelista@gmail.com>,
Peter Grandi <pg@lxra2.for.sabi.co.uk>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid10n2/xfs setup guidance on write-cache/barrier
Date: Fri, 16 Mar 2012 12:06:54 +0100 [thread overview]
Message-ID: <3633779.GerkmFcqtU@saturn> (raw)
In-Reply-To: <CAA8mOyC-xCcNxQFz-M1_TfnxcGBmpUdQ57_vYNVF11jhWK3SSA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Am Freitag, 16. März 2012, 11:36:07 schrieb Jessie Evangelista:
> If you were in my place with the resource constraints, you'd go with:
> xfs with barriers on top of mdraid10 with device cache ON and setting
> vm/dirty_bytes, vm/dirty_background_bytes, vm/dirty_expire_centisecs,
> vm/dirty_writeback_centisecs to safe values
If you ever experienced a crash where lots of sensible and important
data were lost, you would not even think about "device cache ON".
> could you please suggest a hardware raid card with BBU that's cheap?
"Cheap" is a varying definition. How much is your data worth? How much
does one day of blackout cost?
I've been very happy with Areca Controllers, like the 12x0 and 1680
series, and now there's the newer 1882 series like
http://geizhals.at/eu/721745
plus a BBU for about 100€.
You can even mix RAID levels on the same disks, example of 8x1TB define
a RAID0 of 500G and the rest a RAID6. Online expansion possible,
scheduled background verify, e-mail notification on everything, logging,
ntp times, oob-mgmnt via it's own network interface, ...
Very reliable, I never had a problem. And they have a good support team.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-16 11:06 UTC|newest]
Thread overview: 32+ 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 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 [this message]
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
[not found] ` <4F64115D.50208@hardwarefreak.com>
[not found] ` <20120317223454.GQ5091@dastard>
2012-03-18 2:09 ` raid10n2/xfs setup guidance on write-cache/barrier 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-16 12:25 ` 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-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=3633779.GerkmFcqtU@saturn \
--to=michael.monnerie@is.it-management.at \
--cc=jessie.evangelista@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=pg@lxra2.for.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;
as well as URLs for NNTP newsgroup(s).