From: Neil Brown <neilb@suse.de>
To: Turbo Fredriksson <turbo@bayour.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Moving MD/LVM from PPC to x86
Date: Sat, 30 Jun 2007 19:33:27 +1000 [thread overview]
Message-ID: <18054.9063.45466.586046@notabene.brown> (raw)
In-Reply-To: message from Turbo Fredriksson on Saturday June 30
On Saturday June 30, turbo@bayour.com wrote:
> Quoting Alasdair G Kergon <agk@redhat.com>:
>
> > On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
> >> 2. How do I move a VG/PV/LV from PPC to x86?
> >
> > The on-disk LVM2 metadata should be accessible from both
> > architectures.
>
> Well, when I move the disks, the intel machine say that one of
> the disks don't have a partition table and that the other don't
> have any MD superblock...
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
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.
NeilBrown
next prev parent reply other threads:[~2007-06-30 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 21:02 Turbo Fredriksson
2007-06-29 21:54 ` Alasdair G Kergon
2007-06-30 9:09 ` Turbo Fredriksson
2007-06-30 9:33 ` Neil Brown [this message]
2007-07-02 14:52 ` John Stoffel
2007-07-04 19:05 ` Turbo Fredriksson
2007-07-08 20:15 ` Turbo Fredriksson
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=18054.9063.45466.586046@notabene.brown \
--to=neilb@suse.de \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=turbo@bayour.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
all inboxes | Powered by JetHome®