linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Iustin Pop <iusty@k1024.org>
Cc: "J. David Beutel" <jdb@getsu.com>,
	Richard Scobie <richard@sauce.co.nz>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: reducing the number of disks a RAID1 expects
Date: Tue, 11 Sep 2007 16:04:08 +0200	[thread overview]
Message-ID: <18150.41048.240735.467994@notabene.brown> (raw)
In-Reply-To: message from Iustin Pop on Monday September 10

On Monday September 10, iusty@k1024.org wrote:
> On Sun, Sep 09, 2007 at 09:31:54PM -1000, J. David Beutel wrote:
> > [root@samue ~]# mdadm --grow /dev/md5 -n2
> > mdadm: Cannot set device size/shape for /dev/md5: Device or resource busy
> >
> > mdadm - v1.6.0 - 4 June 2004
> > Linux 2.6.12-1.1381_FC3 #1 Fri Oct 21 03:46:55 EDT 2005 i686 athlon i386 
> > GNU/Linux
> 
> I'm not sure that such an old kernel supports reshaping an array. The
> mdadm version should not be a problem, as that message is probably
> generated by the kernel.

2.6.12 does support reducing the number of drives in a raid1, but it
    will only remove drives from the end of the list. e.g. if the
    state was

      58604992 blocks [3/2] [UU_]

then it would work.  But as it is

      58604992 blocks [3/2] [_UU]

it won't.  You could fail the last drive (hdc8) and then add it back
in again.  This would move it to the first slot, but it would cause a
full resync which is a bit of a waste.

Since commit 6ea9c07c6c6d1c14d9757dd8470dc4c85bbe9f28 (about
2.6.13-rc4) raid1 will repack the devices to the start of the
list when trying to change the number of devices.

> 
> I'd recommend trying to boot with a newer kernel, even if only for the
> duration of the reshape.
> 

Yes, a kernel upgrade would do the trick.

NeilBrown

  parent reply	other threads:[~2007-09-11 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10  1:10 reducing the number of disks a RAID1 expects J. David Beutel
2007-09-10  2:29 ` Richard Scobie
2007-09-10  7:31   ` J. David Beutel
2007-09-10  9:55     ` Iustin Pop
2007-09-11 13:33       ` Bill Davidsen
2007-09-11 14:04       ` Neil Brown [this message]
2007-09-15 21:13         ` J. David Beutel
2007-09-16 22:09           ` Goswin von Brederlow

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=18150.41048.240735.467994@notabene.brown \
    --to=neilb@suse.de \
    --cc=iusty@k1024.org \
    --cc=jdb@getsu.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    /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).