linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "3tcdgwg3" <3tcdgwg3@prodigy.net>
To: Mike Tran <mhtran@us.ibm.com>, Matthew Mitchell <matthew@geodev.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Move md raid5 from intel to sparc?
Date: Wed, 11 Jun 2003 12:31:03 -0700	[thread overview]
Message-ID: <00c701c33050$00057360$7b07a8c0@pluto> (raw)
In-Reply-To: 1055359074.1929.70.camel@langvan.austin.ibm.com

I am doing a sparc thingin. I have to build
the disk images on a x86 system, and move the
disk to my sparc, for debug/test.  Everhting works
fine, except the MD's SB.  I tweaked a bit on MD
driver, then everything is good.  I would think that
MD should take care the SB format in next release.


----- Original Message ----- 
From: "Mike Tran" <mhtran@us.ibm.com>
To: "Matthew Mitchell" <matthew@geodev.com>
Cc: <linux-raid@vger.kernel.org>
Sent: Wednesday, June 11, 2003 12:17 PM
Subject: Re: Move md raid5 from intel to sparc?


> On Wed, 2003-06-11 at 13:03, Matthew Mitchell wrote:
> 
> > 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?
> 
> Just look at the current releases of kernel, 2.4 and 2.5, all of the
> above filesytems seem to write metadata using one known byte-order (ei.
> always BE or always LE).  Now all we need is testing.
> 
> -Mike Tran
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2003-06-11 19:31 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
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 [this message]
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='00c701c33050$00057360$7b07a8c0@pluto' \
    --to=3tcdgwg3@prodigy.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=matthew@geodev.com \
    --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).