linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Mitchell <matthew@geodev.com>
To: Mike Tran <mhtran@us.ibm.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Move md raid5 from intel to sparc?
Date: Wed, 11 Jun 2003 13:03:06 -0500	[thread overview]
Message-ID: <3EE76EDA.1060000@geodev.com> (raw)
In-Reply-To: <1055350640.1929.28.camel@langvan.austin.ibm.com>

Mike Tran wrote:
> On Wed, 2003-06-11 at 10:02, Matthew Mitchell wrote:
> 
>>Hello everyone,
>>
>>In the interest of keeping around some otherwise-functional Sparcs, I 
>>was asked if it would be possible to move a linux md raid set from an 
>>Intel box to a Sun box.  I said, "Sure," and then immediately wondered 
>>about byte ordering -- will this work?  Take the SCSI box off of the 
>>intel, plug it into the sparc, and try to run the array...
>>
>>Then my next thought was that someone here would know the answer. :)
>>
> 
> 
> It will not work. The on-disk MD superblock is written using cpu arch
> format.  Furthermore, let's say you are able to re-create the raid5
> array after moving it to the Sun box.  What about the filesystem and
> data?  At least you need a filesystem which manipulates its metadata in
> neutral format for this kind of "move" to work.

As I feared.

What _about_ the filesystem and data, though?  Some filesystems are 
certainly written in a known byte-order, like ISO 9660.  Are there any 
of (ext3, XFS, JFS, reiserfs) that this is true for?  Or are they all 
written in cpu native byte-order?

-- 
Matthew Mitchell
Systems Programmer/Administrator            matthew@geodev.com
Geophysical Development Corporation         phone 713 782 1234
1 Riverway Suite 2100, Houston, TX  77056     fax 713 782 1829


  reply	other threads:[~2003-06-11 18:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 15:02 Move md raid5 from intel to sparc? Matthew Mitchell
2003-06-11 16:57 ` Mike Tran
2003-06-11 18:03   ` Matthew Mitchell [this message]
2003-06-11 19:08     ` Matt Stegman
2003-06-11 20:44       ` Matti Aarnio
2003-06-11 21:16         ` Tom Vier
2003-06-11 19:17     ` Mike Tran
2003-06-11 19:31       ` 3tcdgwg3
2003-06-11 19:50         ` Mike Tran
2003-06-11 20:12           ` Paul Clements
2003-06-12 14:45             ` Matthew Mitchell
2003-06-12 15:04               ` Paul Clements
2003-06-13  5:29               ` Neil Brown
2003-06-11 19:24 ` Cal Webster

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=3EE76EDA.1060000@geodev.com \
    --to=matthew@geodev.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mhtran@us.ibm.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;
as well as URLs for NNTP newsgroup(s).