From: Andre Noll <maan@systemlinux.org>
To: Zdenek Behan <rain@matfyz.cz>
Cc: mmclagan+reply@invlogic.com,
Michael McLagan <mmclagan@invlogic.com>,
linux-raid@vger.kernel.org
Subject: Re: Size limitation?
Date: Sun, 3 Jan 2010 21:33:36 +0100 [thread overview]
Message-ID: <20100103203336.GM21495@skl-net.de> (raw)
In-Reply-To: <4B3E85B3.6080607@matfyz.cz>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On 00:30, Zdenek Behan wrote:
> On 01/01/2010 08:57 PM, Michael McLagan wrote:
> > I'm trying to set up a large array but isn't working. I tried
> > Googling size limits, etc and came up empty.
> >
> > The problem is that with 10 drives (300GB SCSI), the array is coming up
> > with 500GB of space?!? I did an experiment and when the array size
> > exceeds 2TB, it fails/wraps?
> >
> Just curious, did you compile your kernel with LBD (Large Block Device)
> support?
Jup, missing LBD support would explain what Michael is seeing. That
begs the question why md happily creates arrays > 2T on a kernel
witout LBD support..
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-01-03 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 19:57 Size limitation? Michael McLagan
2010-01-01 21:28 ` Kristleifur Daðason
2010-01-01 21:31 ` Kristleifur Daðason
2010-01-01 21:32 ` Joe Landman
2010-01-01 21:42 ` Roger Heflin
2010-01-01 23:00 ` Leslie Rhorer
2010-01-01 23:30 ` Zdenek Behan
2010-01-02 0:46 ` Michael Evans
2010-01-03 20:33 ` Andre Noll [this message]
2010-01-03 23:33 ` mjevans1983
2010-01-03 23:34 ` mjevans1983
2010-01-04 0:29 ` John Robinson
2010-01-03 23:34 ` mjevans1983
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=20100103203336.GM21495@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=mmclagan+reply@invlogic.com \
--cc=mmclagan@invlogic.com \
--cc=rain@matfyz.cz \
/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).