linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: vincent <hanguozhong@meganovo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: make filesystem failed while the capacity of raid5 is big than 16TB
Date: Wed, 12 Sep 2012 09:58:12 +0200	[thread overview]
Message-ID: <50504094.2040302@hesbynett.no> (raw)
In-Reply-To: <505033fe.8aec440a.5d52.ffffe37b@mx.google.com>

On 12/09/2012 09:04, vincent wrote:
> Hi, everyone:
>          I am Vincent, I am writing to you to ask a question about how to
> make file system about my raid5.
>          I created a raid5 with 16 *2T disks, it was OK.
>          Then I used mk2fs to make file system for the raid5.
>          Unfortunately, it was failed.
>          The output was:
>          # mke2fs -t ext4 /dev/md126
>            mke2fs 1.41.12 (17-May-2010)
>            mke2fs: Size of device /dev/md126 too big to be expressed in 32
> bits
>            using a blocksize of 4096.
>          Is anyone had the same problem? Could you help me?
>          The version of my mdadm is 3.2.2, and the version of my kernel is
> 2.6.38
>          Thanks.
>

You need e2fsprogs version 1.42 or above to create an ext4 filesystem 
larger than 16 TB.

However, it is more common to use XFS for such large filesystems.

Another possibility is putting an LVM physical volume on the array and 
making multiple smaller logical partitions for your filesystem.

Almost certainly, however, a raid5 of 16 disks is a bad idea. 
Performance for writes will be terrible, as will parallel reads and 
writes (though that will improve dramatically as the current 
developments in multi-threaded raid5 make their way into mainstream 
distros).  And it is very poor from a reliability viewpoint - your risk 
of a second failure during a rebuild is high with a 16 disk raid5.

What is your actual application here?  If you tell us how this system 
will be used, it will be a lot easier to advise you on a better solution 
(perhaps a raid6, perhaps a raid10, perhaps a number of raid5 systems 
connected with raid0, perhaps multiple raid0 or raid5 arrays with a 
linear concatenation and XFS).


  parent reply	other threads:[~2012-09-12  7:58 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 [this message]
     [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
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=50504094.2040302@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=hanguozhong@meganovo.com \
    --cc=linux-raid@vger.kernel.org \
    /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).