From: Turbo Fredriksson <turbo@bayour.com>
To: linux-kernel@vger.kernel.org
Cc: Neil Brown <neilb@suse.de>, Alasdair G Kergon <agk@redhat.com>
Subject: Re: Moving MD/LVM from PPC to x86
Date: Sun, 08 Jul 2007 22:15:03 +0200 [thread overview]
Message-ID: <873azy4pq0.fsf@pumba.bayour.com> (raw)
In-Reply-To: <18054.9063.45466.586046@notabene.brown> (Neil Brown's message of "Sat, 30 Jun 2007 19:33:27 +1000")
Quoting Neil Brown <neilb@suse.de>:
> Version 0.90 MD superblocks (still the default) uses host-endian
> values so you cannot move between architectures directly. However
> isn't too hard to make it work.
> Firstly, use
> mdadm --examine --metadata=0.swap /dev/DEVICE
----- s n i p -----
ppc:~# mdadm --examine --metadata=0.swap /dev/md0
mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got 00000000)
ppc:~# mdadm --examine --metadata=0.swap /dev/md1
mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got 00000000)
ppc:~# mdadm --examine --metadata=0.swap /dev/md2
mdadm: No super block found on /dev/md2 (Expected magic a92b4efc, got 00000000)
ppc:~# mdadm --examine --metadata=0.swap /dev/sda1
mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# mdadm --examine --metadata=0.swap /dev/sda
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000)
ppc:~# mdadm --examine --metadata=0.swap /dev/sdb
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000)
ppc:~# mdadm --examine --metadata=0.swap /dev/sdb1
mdadm: No super block found on /dev/sdb1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# mdadm --examine --metadata=0.swap /dev/sdc
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000)
ppc:~# mdadm --examine --metadata=0.swap /dev/sdc1
mdadm: No super block found on /dev/sdc1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# cat /proc/mdstat | grep ^md
md2 : active raid1 sdb1[0]
md1 : active raid1 sdc1[0]
md0 : active raid1 sda1[0]
----- s n i p -----
Now what?
> to check that you have the right devices.
> Then
>
> mdadm --assemble /dev/md0 --update=byteorder /dev/DEV0 /dev/DEV1 ....
>
> That should assemble the array and update the superblocks so that they
> are in the right byteorder and will assemble easily in future.
Is this safe, changing the byteorder on all the physical devices (that are
part of my MD's)?
Will it still work on the PPC?
next prev parent reply other threads:[~2007-07-08 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 21:02 Moving MD/LVM from PPC to x86 Turbo Fredriksson
2007-06-29 21:54 ` Alasdair G Kergon
2007-06-30 9:09 ` Turbo Fredriksson
2007-06-30 9:33 ` Neil Brown
2007-07-02 14:52 ` John Stoffel
2007-07-04 19:05 ` Turbo Fredriksson
2007-07-08 20:15 ` Turbo Fredriksson [this message]
2007-07-09 5:34 ` Neil Brown
2007-07-09 9:48 ` Turbo Fredriksson
2007-07-11 9:24 ` Turbo Fredriksson
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=873azy4pq0.fsf@pumba.bayour.com \
--to=turbo@bayour.com \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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