public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "NeilBrown" <neilb@suse.de>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: linux raid <linux-raid@vger.kernel.org>
Subject: Re: mdadm can't reshape/resize arrays
Date: Thu, 25 Jun 2009 08:07:13 +1000 (EST)	[thread overview]
Message-ID: <b1d80cbeaf61f9b8496e31f0a57df951.squirrel@neil.brown.name> (raw)
In-Reply-To: <878wjh4qt1.fsf@frosties.localdomain>

On Thu, June 25, 2009 1:03 am, Goswin von Brederlow wrote:
> Hi,
>
> I'm trying to resize/reshape some of my arrays:
>
> md1 : active raid1 sdc5[1]
>       9767424 blocks [2/1] [_U]
>       bitmap: 48/150 pages [192KB], 32KB chunk
>
> % mdadm --grow --size max /dev/md1
> mdadm: Cannot set device size for /dev/md1: Device or resource busy
>
> and dmesg says:
>   md: couldn't update array info. -16
>
>
> md2 : active raid5 sdc2[6](S) sde2[3] sdg1[1] sdf3[4] sdd1[5] sdb1[2]
> sda1[0]
>       945625280 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
>       bitmap: 0/181 pages [0KB], 512KB chunk
>
> % mdadm --grow -n 7 /dev/md2
> mdadm: Need to backup 1920K of critical section..
> mdadm: Cannot set device size/shape for /dev/md2: Device or resource busy
>
> and dmesg says:
>   md: couldn't update array info. -16
>
>
> % uname -a
> Linux frosties 2.6.29.4-frosties-1 #8 Sun Jun 7 00:48:55 CEST 2009 x86_64
> GNU/Linux
>
> % mdadm --version
> mdadm - v2.6.9 - 10th March 2009
>
>
> Anyone have an idea what is wrong there?

md cannot grow arrays with bitmaps as it is not able to grow the bitmap.
You need to remove the bitmap, grow the array, then add the bitmap.
And unfortunately you cannot add the bitmap until the grow
has finished.

Yes, there is room for improvement here.

NeilBrown


  reply	other threads:[~2009-06-24 22:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 15:03 mdadm can't reshape/resize arrays Goswin von Brederlow
2009-06-24 22:07 ` NeilBrown [this message]
2009-06-25  8:20   ` 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=b1d80cbeaf61f9b8496e31f0a57df951.squirrel@neil.brown.name \
    --to=neilb@suse.de \
    --cc=goswin-v-b@web.de \
    --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