From: Kasper Sandberg <lkml@metanurb.dk>
To: linux-raid@vger.kernel.org
Subject: RE: problem in grow of raid5 3 -> 4 disks
Date: Wed, 18 Feb 2009 02:52:39 +0100 [thread overview]
Message-ID: <1234921959.18827.33.camel@localhost> (raw)
In-Reply-To: <1234905178.18827.25.camel@localhost>
Hello again
Seems he was impatient, and just recompiled kernel and rebooted - and it
worked, it continued the reshape and all is well :)
On Tue, 2009-02-17 at 22:12 +0100, Redeeman wrote:
> (sorry its not properly threaded, but message didnt show up via
> mailinglist yet)
>
> To add some information, i think the culprit is that he forgot support
> for large block devices in kernel (its 32bit x86)..
>
> What is the recommendation based on this? enable support, and reboot?
>
>
> Thanks again.
>
> --
> 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:[~2009-02-18 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 21:12 problem in grow of raid5 3 -> 4 disks Redeeman
2009-02-18 1:52 ` Kasper Sandberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 20:48 Redeeman
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=1234921959.18827.33.camel@localhost \
--to=lkml@metanurb.dk \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.