From: Neil Brown <neilb@suse.de>
To: Thorsten Wolf <T_Wolf@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
Date: Tue, 12 Jun 2007 17:34:55 +1000 [thread overview]
Message-ID: <18030.19615.898281.457910@notabene.brown> (raw)
In-Reply-To: message from Thorsten Wolf on Tuesday June 12
On Tuesday June 12, T_Wolf@gmx.net wrote:
> Hello everyone.
>
> I've got a SLES9 SP3 running and I've been quite happy with it so far.
>
> Recently, I've created a 4 disk spanning RAID-5 on our company
> server. Runs quite nice and we're happy with that too. I created
> that RAID using the SLES mdadm (1.4 I believe) package.
>
> After discovering that there is a much newer mdadm out here (2.6.1),
> I decided to upgrade. It went just fine. Raid still running at 120
> MB/sec.
>
> After adding a disk to the raid, which went fine as well...... BUT:
>
> The added disk /dev/sda1 shows up in /proc/mdstat, but does not have
> the "spare (s)" flag.
>
> Plus... the --grow doesn't work...
>
> I get the: mdadm: /dev/md0: Cannot get array details from sysfs
> error which has been discussed before. Can it be that this is caused
> by the 2.6.5-7.2xx Kernel? Any ideas?
Yes. All of your issues are caused by using a 2.6.5 based kernel.
However even upgrading to SLES10 would not get you raid5-grow. That
came a little later. You would need to compile a mainline kernel or
wait for SLES11.
NeilBrown
next prev parent reply other threads:[~2007-06-12 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 7:24 SLES 9 SP3 and mdadm 2.6.1 (via rpm) Thorsten Wolf
2007-06-12 7:34 ` Neil Brown [this message]
2007-06-12 16:56 ` Bill Davidsen
2007-06-15 8:16 ` need help in recovering a RAID Thorsten Wolf
2007-06-13 11:45 ` SLES 9 SP3 and mdadm 2.6.1 (via rpm) Thorsten Wolf
2007-06-13 11:50 ` Justin Piszcz
2007-06-14 7:53 ` Luca Berra
2007-06-14 8:22 ` Justin Piszcz
2007-06-16 16:44 ` Luca Berra
2007-06-25 19:17 ` Thorsten Wolf
2007-06-25 19:28 ` 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=18030.19615.898281.457910@notabene.brown \
--to=neilb@suse.de \
--cc=T_Wolf@gmx.net \
--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 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).