linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Heflin <rogerheflin@gmail.com>
To: mmclagan+reply@invlogic.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Size limitation?
Date: Fri, 01 Jan 2010 15:42:35 -0600	[thread overview]
Message-ID: <4B3E6C4B.20604@gmail.com> (raw)
In-Reply-To: <201001011457.24334.mmclagan@invlogic.com>

Michael McLagan wrote:
> Hello,
> 
>    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?
> 
> Is there a solution (simple or otherwise) for this?  The machine runs 
> 2.6.29.5 (anything later causes the machine to lock up :( ).  I'm not 
> sure if mdadm or the kernel is the problem either.
> 
> Any suggestions appreciated (please CC me on replies).
> 
>    Michael
> 
>

Just guessing it is a mdadm bug.

I have a 32-bit 2.6.27.5 machine with mdadm 2.6.7 and mine is showing 
an array size of 4.5tb correctly, so 2.6.29 should be just fine.

Check mdadm --version and see what version that you have of that, you 
might also mount up the array and do "cat /proc/mdstat" and see what 
size the kernel reports.

  parent reply	other threads:[~2010-01-01 21:42 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 [this message]
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
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=4B3E6C4B.20604@gmail.com \
    --to=rogerheflin@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mmclagan+reply@invlogic.com \
    /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).