From: Bill Davidsen <davidsen@tmr.com>
To: Iain Rauch <groups@email.iain.rauch.co.uk>
Cc: Neil Brown <neilb@suse.de>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
Justin Piszcz <jpiszcz@lucidpixels.com>
Subject: Re: RAID 6 grow problem
Date: Mon, 04 Jun 2007 16:29:02 -0400 [thread overview]
Message-ID: <4664760E.8040606@tmr.com> (raw)
In-Reply-To: <C287AF46.7EDF%groups@email.iain.rauch.co.uk>
Iain Rauch wrote:
>>>> raid6 reshape wasn't added until 2.6.21. Before that only raid5 was
>>>> supported.
>>>> You also need to ensure that CONFIG_MD_RAID5_RESHAPE=y.
>>>>
>>> I don't see that in the config. Should I add it? Then reboot?
>>>
>> You reported that you were running a 2.6.20 kernel, which doesn't
>> support raid6 reshape.
>> You need to compile a 2.6.21 kernel (or
>> apt-get install linux-image-2.6.21-1-amd64
>> or whatever) and ensure that CONFIG_MD_RAID5_RESHAPE=y is in the
>> .config before compiling.
>>
>
> There only seems to be version 2.6.20 does this matter a lot? Also how do I
> specify what is in the config when using apt-get install?
>
2.6.20 doesn't support the feature you want, only you can tell if that
matters a lot. You don't, either get a raw kernel source and configure,
or run what the vendor provides for config. Sorry, those are the option.
>
>>> I used apt-get install mdadm to first install it, which gave me 2.5.x then I
>>> downloaded the new source and typed make then make install. Now mdadm -V
>>> shows "mdadm - v2.6.2 - 21st May 2007".
>>> Is there anyway to check it is installed correctly?
>>>
>> The "mdadm -V" check is sufficient.
>>
>
> Are you sure because at first I just did the make/make install and mdadm -V
> did tell me v2.6.2 but I don't believe it was installed properly because it
> didn't recognise my array nor did it make a config file, and cat
> /proc/mdstat said no file/directory??
mdadm doesn't control the /proc/mdstat file, it's written by the kernel.
The kernel had no active array to mention in the mdstat file.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-06-04 20:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0706021232040.13184@p34.internal.lan>
2007-06-02 21:26 ` RAID 6 grow problem Iain Rauch
2007-06-02 21:31 ` Justin Piszcz
2007-06-02 21:33 ` Justin Piszcz
2007-06-02 21:38 ` Neil Brown
2007-06-02 21:55 ` Iain Rauch
2007-06-02 22:07 ` Neil Brown
2007-06-02 22:35 ` Iain Rauch
2007-06-03 23:33 ` Daniel Korstad
2007-06-04 6:47 ` RAID6 clean? Guy Watkins
2007-06-04 6:59 ` Neil Brown
2007-08-18 5:40 ` Guy Watkins
2007-06-04 20:29 ` Bill Davidsen [this message]
2007-06-05 17:08 ` RAID 6 grow problem Iain Rauch
2007-06-05 19:21 ` Daniel Korstad
2007-06-05 21:26 ` Jon Nelson
2007-06-06 0:46 ` Neil Brown
2007-06-10 19:18 ` Iain Rauch
2007-06-10 20:17 ` Justin Piszcz
2007-06-06 15:06 Daniel Korstad
2007-06-06 15:38 ` Jon Nelson
2007-06-07 4:44 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2007-06-02 15:30 Iain Rauch
2007-06-02 16:19 ` Justin Piszcz
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=4664760E.8040606@tmr.com \
--to=davidsen@tmr.com \
--cc=groups@email.iain.rauch.co.uk \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).