From: Michael Evans <mjevans1983@gmail.com>
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: Fri, 1 Jan 2010 16:46:56 -0800 [thread overview]
Message-ID: <4877c76c1001011646y6e5826ddx5b360e2cfdb2e28a@mail.gmail.com> (raw)
In-Reply-To: <4B3E85B3.6080607@matfyz.cz>
On Fri, Jan 1, 2010 at 3:30 PM, Zdenek Behan <rain@matfyz.cz> 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?
>
>
> Zdenek
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I couldn't find it in my config, so I googled:
http://cateee.net/lkddb/web-lkddb/LBD.html That does look like the
most likely problem.
If at all possible try to get a good dmesg capture of a new kernel,
you might want to explore using netconsole to log via UDP to a remote
system. Chances are good it's just some chipset/driver issue; I
remember having problems with a lack of timer for some boards; either
forcing it to use the older style timer or using a patched bios which
properly setup the HPET (timer) resolved the issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-02 0:46 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 [this message]
2010-01-03 20:33 ` Andre Noll
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=4877c76c1001011646y6e5826ddx5b360e2cfdb2e28a@mail.gmail.com \
--to=mjevans1983@gmail.com \
--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).