From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: linux-raid@vger.kernel.org
Cc: mmclagan+reply@invlogic.com
Subject: Re: Size limitation?
Date: Fri, 1 Jan 2010 21:28:51 +0000 [thread overview]
Message-ID: <73e903671001011328t24405d6oaf418d2b75cd42ca@mail.gmail.com> (raw)
In-Reply-To: <201001011457.24334.mmclagan@invlogic.com>
On Fri, Jan 1, 2010 at 7:57 PM, Michael McLagan <mmclagan@invlogic.com> 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?
>
Looked at the mdadm output and ... Wow that's strange. You aren't
supposed to be hitting any size limits there as far as I know, and I
can't see that you're doing anything wrong - The "wraparound" just
shouldn't be happening in my opinion. (But I'm a RAID rookie so don't
take that as an expert judgement. Perhaps rather as some solidarity in
a strange situation.) Anyway ...
> 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.
>
That's kinda scary. Is this some unusual architecture or hardware
configuration? I don't want to take this off-topic if you have
determined the kernel version to be a fixed variable, but: Do you know
why a newer kernel won't go? To me, newer-kernels-crashing indicates
an irregularity under the hood.
> Any suggestions appreciated
Try upgrading mdadm. Either latest 2.x or 3.1.x. What the hey, try
both. It's quite easy to compile mdadm yourself, and its for-stability
releases are usually that: More stable. I've built mdadm a number of
times when fooling around and it has always been quite good to me.
(I.e. no exploding-in-face.)
Good luck!
-- Kristleifur
--
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-01 21:28 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 [this message]
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
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=73e903671001011328t24405d6oaf418d2b75cd42ca@mail.gmail.com \
--to=kristleifur@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).