linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: david@lang.hm
To: Neil Brown <neilb@suse.de>
Cc: Jeff Zheng <Jeff.Zheng@endace.com>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-raid@vger.kernel.org, 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 21:45:41 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705162145060.31624@asgard.lang.hm> (raw)
In-Reply-To: <17995.49602.427417.500049@notabene.brown>

On Thu, 17 May 2007, Neil Brown wrote:

> On Thursday May 17, Jeff.Zheng@endace.com wrote:
>>
>>> The only difference of any significance between the working
>>> and non-working configurations is that in the non-working,
>>> the component devices are larger than 2Gig, and hence have
>>> sector offsets greater than 32 bits.
>>
>> Do u mean 2T here?, but in both configuartion, the component devices are
>> larger than 2T (2.25T&5.5T).
>
> Yes, I meant 2T, and yes, the components are always over 2T.

2T decimal or 2T binary?

> So I'm
> at a complete loss.  The raid0 code follows the same paths and does
> the same things and uses 64bit arithmetic where needed.
>
> So I have no idea how there could be a difference between these two
> cases.
>
> I'm at a loss...
>
> NeilBrown
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  parent reply	other threads:[~2007-05-17  4:53 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 [this message]
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
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.0705162145060.31624@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=Jeff.Zheng@endace.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    --cc=neilb@suse.de \
    /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).