linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: Aaron Botsis <aaron@blight.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 endian question....
Date: Sun, 19 Jun 2005 18:05:22 -0400	[thread overview]
Message-ID: <42B5EC22.4030906@steeleye.com> (raw)
In-Reply-To: <61C14314-53E9-4140-A4DB-3929A683FE67@blight.com>

Aaron Botsis wrote:
> I'm attempting to move a raid5 array from a big endian ppc machine to  a 
> little endian x86.

> Upon trying to import the array, I get:
> mdadm: No super block found on /dev/hde1 (Expected magic a92b4efc,  got 
> fc4e2ba9)

> I assume this to be an endianess issue...

Yes.

> Is this a bug? Is just the magic number whacked? or are the  superblock 
> data structures too?

The version 0.90 superblock is not "endian agnostic". It records data in 
whatever endian order the host machine is (Version 1 superblocks, by the 
way, fix this, but are not available unless you have the latest 2.6 
kernel and mdadm).

> what's the best way to fix this?

Unfortunately, I don't think there's an easy way. But, if you can get 
the array back up on the original machine and copy down all the 
information (or if you already have it) then you can re-create the array 
on the x86 machine using "mdadm -C", but be careful... :)

--
Paul

  reply	other threads:[~2005-06-19 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-19  6:14 raid5 endian question Aaron Botsis
2005-06-19 22:05 ` Paul Clements [this message]
2005-06-20  2:54   ` Aaron Botsis
2005-08-04  5:09 ` Neil Brown

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=42B5EC22.4030906@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=aaron@blight.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;
as well as URLs for NNTP newsgroup(s).