From: Peter Hoeg <peter@hoeg.com>
To: linux-raid@vger.kernel.org
Subject: Add BBL to existing array
Date: Wed, 27 Aug 2014 18:32:13 +0800 [thread overview]
Message-ID: <20140827103213.GE15857@dolores.internal.speartail.com> (raw)
In-Reply-To: <20140827192721.57c57c3b@notabene.brown>
Hi,
this isn't so much a question as it trying to document the situation
with BBL's on Debian jessie, although if I've overlooked something,
please let me know.
Purpose: Add BBL to a RAID created by an earlier version of mdadm
without BBL support.
# mdadm --version
mdadm - v3.3 - 3rd September 2013
# uname -a
Linux edith 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux
# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sda2[0] sdd2[4] sdc2[3] sdb2[1]
5859439616 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 1/2 pages [4KB], 1048576KB chunk
unused devices: <none>
As the system boots from the RAID, I thought I could be clever and
simply edit /usr/share/initramfs-tools/scripts/local-top/mdadm and
change the "--assemble" statements to add "--update=bbl" which should
take care of things after a reboot.
It basically runs:
# mdadm --assemble --scan --run --auto=yes
so it would become:
# mdadm --assemble --update=bbl --scan --run --auto=yes
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.
Now, according to the manual with the version of mdadm on the machine,
'--update=bbl' is supported, however when asking mdadm directly, it
doesn't seem to be the case:
# mdadm --assemble --update=?
mdadm: Valid --update options are:
'sparc2.2', 'super-minor', 'uuid', 'name', 'resync',
'summaries', 'homehost', 'byteorder', 'devicesize',
'no-bitmap', 'metadata', 'revert-reshape'
So in all likelyhood, this is a Debian packaging issue.
If anyone answers, please CC me as I am not subscribed to the list, thanks.
--
Regards,
Peter
next parent reply other threads:[~2014-08-27 10:32 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 ` Peter Hoeg [this message]
2014-08-27 11:07 ` Add BBL to existing array NeilBrown
2014-08-27 11:29 ` Peter Hoeg
2014-08-27 11:52 ` NeilBrown
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=20140827103213.GE15857@dolores.internal.speartail.com \
--to=peter@hoeg.com \
--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