From: Turbo Fredriksson <turbo@bayour.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Moving MD/LVM from PPC to x86
Date: Mon, 09 Jul 2007 11:48:46 +0200 [thread overview]
Message-ID: <87r6nh3o1t.fsf@pumba.bayour.com> (raw)
In-Reply-To: <18065.51428.849286.225118@notabene.brown> (Neil Brown's message of "Mon, 9 Jul 2007 15:34:28 +1000")
Quoting Neil Brown <neilb@suse.de>:
> This suggests that the superblock is currently the correct byteorder
> for the current host. You use
> mdadm --examine --metadata=0.swap /dev/sda1
> when you have moved a devices from one host to different host with the
> opposite endian-ness (e.g. bigendian to littlendian).
I see, thanx for clarifying this.
> Does that make it clear?
Absolutely. I just want to be very clear. I don't have a full backup
(have no means to backup 1Tb), so I want to minimize the risk of loosing
data. I thank you for explaining so that even I can understand :)
PS. No sarcasm intended, even IF it should sound like it! I _am_ greatfull.
--
Noriega Honduras Marxist South Africa president AK-47 FSF radar FBI
congress class struggle SEAL Team 6 colonel Cocaine DES
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
next prev parent reply other threads:[~2007-07-09 9:48 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
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 [this message]
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=87r6nh3o1t.fsf@pumba.bayour.com \
--to=turbo@bayour.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®