linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathias Buren <mathias.buren@gmail.com>
To: GuoZhong Han <hanguozhong@meganovo.com>
Cc: David Brown <david.brown@hesbynett.no>,
	stan@hardwarefreak.com, linux-raid@vger.kernel.org
Subject: Re: make filesystem failed while the capacity of raid5 is big than 16TB
Date: Thu, 13 Sep 2012 11:34:02 +0800	[thread overview]
Message-ID: <5051542A.4090901@gmail.com> (raw)
In-Reply-To: <CACY-59dAbS=8ncRAeZrAYBAvo7G6FEyoGREHtC-ze4cwhiF9GQ@mail.gmail.com>

On 13/09/12 11:21, GuoZhong Han wrote:
> Hi David:
>
>           I am sorry for last mail that I had not described the
> requirements of the system very clear.
>
>           I will detail for you to describe the requirements of the system.
>

(snip)

>
>           As you said, the performance for write of 16*2T raid5 will be
> terrible, so what do you think that how many disks to be build to a
> raid5 will be more appropriate?

Personally I wouldn't use more than 5 drives in a RAID5 with drives 
larger than 1TB, the failure risk is too high. With 16x 2TB drives, how 
about two RAID6 arrays of 8 drives each, then RAID0 them? (RAID60)

Or, two RAID6 arrays with 7 drives each, 2 hotspares, and RAID0 on top. 
(RAID10 + 2 HSP)

You mention 36 cores. Perhaps you should try the very latest mdadm 
versions and Linux kernels (perhaps from the MD Linux git tree), and 
enable the multicore option.

Mathias

  reply	other threads:[~2012-09-13  3:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  7:04 make filesystem failed while the capacity of raid5 is big than 16TB vincent
2012-09-12  7:32 ` Jack Wang
2012-09-12  7:37 ` Chris Dunlop
2012-09-12  7:58 ` David Brown
     [not found]   ` <CACY-59cLmV2SRY+FrvhHxseDD1+r-B-3bOKPGzJdGttW+9U2mw@mail.gmail.com>
2012-09-12  9:46     ` David Brown
2012-09-12 14:13       ` Stan Hoeppner
2012-09-13  7:06         ` David Brown
2012-09-13  3:21       ` GuoZhong Han
2012-09-13  3:34         ` Mathias Buren [this message]
2012-09-13  7:13           ` David Brown
2012-09-13  7:30         ` David Brown
2012-09-13  7:43           ` John Robinson
2012-09-13  9:15             ` David Brown
2012-09-13 13:25         ` Stan Hoeppner
2012-09-13 13:52           ` David Brown
2012-09-13 22:47             ` Stan Hoeppner
2012-09-18  9:35           ` GuoZhong Han
2012-09-18 10:22             ` David Brown
2012-09-18 21:38               ` Stan Hoeppner
2012-09-19  7:20                 ` David Brown
2012-09-19 16:00                   ` Stan Hoeppner
2012-09-18 21:20             ` 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=5051542A.4090901@gmail.com \
    --to=mathias.buren@gmail.com \
    --cc=david.brown@hesbynett.no \
    --cc=hanguozhong@meganovo.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=stan@hardwarefreak.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).