From: Robin Hill <robin@robinhill.me.uk>
To: Alex <mysqlstudent@gmail.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Converting RAID1 to RAID5
Date: Fri, 16 Sep 2011 16:10:30 +0100 [thread overview]
Message-ID: <20110916151030.GA14303@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <CAB1R3sj7tPR-N91rJmrVOv1YqwpmC=E=zVxNmjCNYzKsS7mr9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2463 bytes --]
On Fri Sep 16, 2011 at 09:56:58AM -0400, Alex wrote:
> Hi,
>
> For completeness, these are the steps I have followed, assuming a
> RAID1 array is md0:
>
> # mdadm --grow /dev/md0 --bitmap=none
> # mdadm --grow /dev/md0 --level=5 --raid-devices=3
> - wait for reshape to complete
> # mdadm --grow /dev/md0 --bitmap=internal
>
> I noticed there is a difference between one array and another:
>
> md125 : active raid5 sdb1[0] sda1[2] sdc1[1]
> 1023976 blocks super 1.0 level 5, 4k chunk, algorithm 2 [3/3] [UUU]
> bitmap: 0/1 pages [0KB], 65536KB chunk
>
> md126 : active raid5 sdb2[0] sda2[2] sdc2[1]
> 102397816 blocks super 1.1 level 5, 4k chunk, algorithm 2 [3/3] [UUU]
> bitmap: 0/1 pages [0KB], 65536KB chunk
>
> Is that a reference to the superblock? Why would they be different?
> They were both created at the same time with the same fedora15
> versions. This is created at the time the filesystem is created,
> correct?
>
I assume md125 is /boot? This showed up as superblock 1.0 earlier
anyway. You need to use either 0.9 or 1.0 with grub (grub 1 anyway, I've
never used grub 2 so I'm not sure what that handles) as they place the
RAID metadata at the end of the drives. This means grub can access the
drives as though they were independent disks, ignoring the RAID. If you
set these up at install time then I assume Fedora automatically used the
correct superblock.
> It looks like this has also now affected grub, as the system no longer
> boots. Is this expected?
>
> When I try to reinstall grub, it fails with an error relating to /boot:
>
> # grub-install --recheck --root-directory=/mnt/disk /dev/sda
> Probing devices to guess BIOS drives. This may take a long time.
> /dev/md125 does not have any corresponding BIOS drive.
>
> Maybe /boot should be left as RAID1?
>
Yes, grub 1 can only boot from (what it sees as) standalone drives,
(so RAID1 with superblock 0.9 or 1.0 will work as the filesystem is in
exactly the same position as on a non-RAID drive). You'll need to
convert this back, though you can set it up as a 3-disk RAID1, giving
you extra redundancy. I doubt you'd need the extra space there anyway.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-16 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 3:38 Converting RAID1 to RAID5 Alex
2011-09-11 3:57 ` NeilBrown
2011-09-11 15:40 ` Alex
2011-09-15 23:50 ` Alex
2011-09-16 3:57 ` NeilBrown
2011-09-16 13:56 ` Alex
2011-09-16 15:10 ` Robin Hill [this message]
[not found] ` <27910711.10376.1316131253095.JavaMail.mobile-sync@iagt29>
2011-09-16 2:54 ` Jérôme Poulin
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=20110916151030.GA14303@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mysqlstudent@gmail.com \
--cc=neilb@suse.de \
/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).