Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Michael Ryan <mryan@lenovoemc.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: migrate to bad block list
Date: Thu, 16 Oct 2014 17:54:14 +1100	[thread overview]
Message-ID: <20141016175414.01334582@notabene.brown> (raw)
In-Reply-To: <E1D69AD765F9D841B8DE87D96DD21E4505DFBADD@AEMAILMBX02.lenovo.com>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

On Wed, 15 Oct 2014 17:18:19 +0000 Michael Ryan <mryan@lenovoemc.com> wrote:

> 
> Is there any way to migrate an existing array created with mdadm v3.2.5 and using 1.1 metadata to use a bad block list?  I'm assuming not as there wouldn't be space reserved for the list, but I need to ask.
> 
> Thanks for your response!

mdadm tends to leave a fair bit of unused space on devices so that things
like a bad block list can easily be added.
If you can stop the array, then do that and re-assemble with
  --update=bbl

and you should  get a bbl added to each device.

If you cannot stop the array, but it has a bitmap, then
you can, for each device:

  mdadm /dev/mdX --fail /dev/adevice
  mdadm /dev/mdX --remove /dev/adevice
  mdadm /dev/mdX --re-add --update=bbl /dev/adevice

I think that should work.  The "bblk" is a feature of the device, not of the
whole array.  So you can add it to each device.

I haven't actually tested the above I think, so it might be safest to make an
array with loop-back devices and experiment.

NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-10-16  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 17:18 migrate to bad block list Michael Ryan
2014-10-16  6:54 ` NeilBrown [this message]
2014-10-17 17:06   ` Piergiorgio Sartor

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=20141016175414.01334582@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=mryan@lenovoemc.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