linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: david@lang.hm
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Jeff Zheng <Jeff.Zheng@endace.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Software raid0 will crash the file-system, when each disk is 5TB
Date: Wed, 16 May 2007 11:04:16 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705161058430.1280@asgard.lang.hm> (raw)
In-Reply-To: <20070516140452.GC5286@schatzie.adilger.int>

On Wed, 16 May 2007, Andreas Dilger wrote:

> On May 16, 2007  11:09 +1200, Jeff Zheng wrote:
>> We are using two 3ware disk array controllers, each of them is connected
>> 8 750GB harddrives. And we build a software raid0 on top of that. The
>> total capacity is 5.5TB+5.5TB=11TB
>>
>> We use jfs as the file-system, we have a test application that write
>> data continuously to the disks. After writing 52 10GB files, jfs
>> crashed. And we are not able to recover it, fsck doesn't recognise it
>> anymore.
>> We then tried xfs, same application, lasted a little longer, but gives
>> kernel crash later.
>
> Check if your kernel has CONFIG_LBD enabled.
>
> The kernel doesn't check if the block layer can actually write to
> a block device > 2TB.

my experiance is taht if you don't have CONFIG_LBD enabled then the kernel 
will report the larger disk as 2G and everything will work, you just won't 
get all the space.

plus he seems to be crashing around 500G of data

and finally (if I am reading the post correctly) if he configures the 
drives as 4x2.2TB=11TB instead of 2x5.5TB=11TB he doesn't have the same 
problem.

I'm getting ready to setup a similar machine that will have 3x10TB (3 15 
disk arrays with 750G drives), but won't be ready to try this for a few 
more days.

David Lang

  reply	other threads:[~2007-05-16 18:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 23:09 Software raid0 will crash the file-system, when each disk is 5TB Jeff Zheng
2007-05-15 23:29 ` Michal Piotrowski
2007-05-16  0:03   ` Neil Brown
2007-05-16  1:56     ` Jeff Zheng
2007-05-16 17:28       ` Bill Davidsen
2007-05-16 17:58         ` david
2007-05-17  0:48       ` Neil Brown
2007-05-17  2:09         ` Jeff Zheng
2007-05-17  2:45           ` Neil Brown
2007-05-17  3:11             ` Jeff Zheng
2007-05-17  4:32               ` Neil Brown
2007-05-17  5:08                 ` Jeff Zheng
2007-05-17  4:45             ` david
2007-05-17  5:03               ` Neil Brown
2007-05-17  5:31                 ` Neil Brown
2007-05-17  5:38                   ` Jeff Zheng
2007-05-17 22:55                     ` Jeff Zheng
2007-05-18  0:21                       ` Neil Brown
2007-05-22 21:31                       ` Bill Davidsen
2007-05-16 14:04 ` Andreas Dilger
2007-05-16 18:04   ` david [this message]
2007-05-16 18:16     ` Jan Engelhardt
2007-05-16 21:42       ` Jeff Zheng
2007-05-17  7:21         ` Jan Engelhardt
2007-05-17 11:11           ` Neil Brown
2007-05-17 15:30             ` Jan Engelhardt
2007-05-16 21:44     ` Jeff Zheng

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=Pine.LNX.4.64.0705161058430.1280@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=Jeff.Zheng@endace.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).