Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: David Miller <millerdc@fusion.gat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 mdadm --grow bug?
Date: Thu, 13 Sep 2007 19:49:47 +0200	[thread overview]
Message-ID: <18153.30779.865508.713927@notabene.brown> (raw)
In-Reply-To: message from David Miller on Thursday September 13

On Thursday September 13, millerdc@fusion.gat.com wrote:
> Neil,
> 
> On RHEL5 the kernel is 2.6.18-8.1.8. On Ubuntu 7.04 the kernel is  
> 2.6.20-16. Someone on the Arstechnica forums wrote they see the same  
> thing in Debian etch running kernel 2.6.18. Below is a messages log  
> from the RHEL5 system. I have only included the section for creating  
> the RAID6, adding a spare and trying to grow it. There is a one line  
> error when I do the "mdadm --grow" command. It is "md: couldn't  
> update array info. -22."

reshaping raid6 arrays was not supported until 2.6.21.  So you'll need
a newer kernel.

NeilBrown

      reply	other threads:[~2007-09-13 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  0:39 RAID6 mdadm --grow bug? David Miller
2007-09-13 10:52 ` Neil Brown
2007-09-13 17:17   ` David Miller
2007-09-13 17:49     ` Neil Brown [this message]

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=18153.30779.865508.713927@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=millerdc@fusion.gat.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