Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Peter Hoeg <peter@hoeg.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Add BBL to existing array
Date: Wed, 27 Aug 2014 21:52:06 +1000	[thread overview]
Message-ID: <20140827215206.51e6e37e@notabene.brown> (raw)
In-Reply-To: <20140827112908.GF15857@dolores.internal.speartail.com>

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

On Wed, 27 Aug 2014 19:29:08 +0800 Peter Hoeg <peter@hoeg.com> wrote:

> Neil,
> 
> >> It basically runs:
> >> # mdadm --assemble --scan --run --auto=yes
> >>
> >> so it would become:
> >> # mdadm --assemble --update=bbl --scan --run --auto=yes
> >
> >Sorry, --update and --scan are incompatible.
> 
> That explains that...
> 
> >> That didn't work. I ended up in the initramfs and had to manually bring
> >> up the RAID as well as LVM to get the machine booted.
> >
> >That would have been a good time to wield the --update=bbl seeing you were
> >assembling the array anyway.
> 
> I actually did - I ran:
> 
> mdadm --assemble --update=bbl /dev/md0
> 
> Which returned without error, but it doesn't seem to have changed
> anything (or am I looking in the wrong place?)
> 
> # mdadm --detail /dev/md0


A bbl exist separately on each component device.
Try 
   mdadm --examine /dev/sda2

look for
   Bad Block Log : 512 entries available at offset XXX sectors

NeilBrown

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

  reply	other threads:[~2014-08-27 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140827090707.GA15857@dolores.internal.speartail.com>
     [not found] ` <20140827192721.57c57c3b@notabene.brown>
2014-08-27 10:32   ` Add BBL to existing array Peter Hoeg
2014-08-27 11:07     ` NeilBrown
2014-08-27 11:29       ` Peter Hoeg
2014-08-27 11:52         ` NeilBrown [this message]
2014-08-27 12:05           ` Peter Hoeg

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=20140827215206.51e6e37e@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=peter@hoeg.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