From: Mike Hardy <mhardy@h3c.com>
To: Dan Stromberg <strombrg@dcs.nac.uci.edu>, linux-raid@vger.kernel.org
Subject: Re: Can "mdadm" linux RAID go large?
Date: Tue, 07 Jun 2005 16:46:15 -0700 [thread overview]
Message-ID: <42A631C7.2060309@h3c.com> (raw)
In-Reply-To: <1118187516.15459.93.camel@seki.nac.uci.edu>
Not sure about the size limits per se
(http://www.suse.de/~aj/linux_lfs.html has good info there)
I can say that with a very large number of disks, you will hit
single-block read errors quite frequently due to the nature of the math
behind MTBF. This will lead to frequent drive expulsion / rebuild
cycles, as discussed in another thread today.
In another question (you could post them all as one mail,
incidentally...) you asked if it was stable. The only evidence appears
to be anecdotal, but it appears extremely stable to me, even under very
heavy testing - normal new machine cpu/network/ram burn-in tests,
combined with multiple bonnie++ processes hitting the array. Any
problems I've had have been attributable to hardware or hardware drivers
thus far.
There have been problems (like the recent set of looping-resync issues
for instance), but I don't remember hearing any that resulted in data
loss, and they get fixed quickly. Serious problems still leave you with
your data on a set of disks in a known format, which means that it may
be laborious but you can reconstruct. So it "degrades" more gracefully
than the black box that are some hardware raid systems.
It takes care to run well and safely though, as with any machine.
-Mike
Dan Stromberg wrote:
> Can mdadm linux RAID go past 2 terabytes reliably?
>
> Can mdadm linux RAID go past 16 terabytes reliably?
>
next prev parent reply other threads:[~2005-06-07 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 23:38 Can "mdadm" linux RAID go large? Dan Stromberg
2005-06-07 23:46 ` Mike Hardy [this message]
2005-06-07 23:53 ` Dan Stromberg
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=42A631C7.2060309@h3c.com \
--to=mhardy@h3c.com \
--cc=linux-raid@vger.kernel.org \
--cc=strombrg@dcs.nac.uci.edu \
/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).