From: Brent Walsh <blinux_adm@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: endianness of Linux kernel RAID
Date: Mon, 8 Aug 2005 21:49:03 -0700 (PDT) [thread overview]
Message-ID: <20050809044903.97593.qmail@web35308.mail.mud.yahoo.com> (raw)
Neil Brown wrote:
>I decided to try it anyway...
>
>The following patch, when applied to
>mdadm-2.0-devel-3 (Recently
>released) should allow:
>
> mdadm --examine --metadata=0.swap /dev/sda1
>
>which will show the superblock with bytes swapped.
>If that looks right for all devices, then
>
> mdadm --assemble /dev/mdX
>--update=byteorder /dev/sda1 /dev/sdb1 ...
>
>
>will assemble the array after swapping the byte
>order on all devices. Once it has been assembled
>this way, the superblocks will have the correct
>byte order, and in future the array can be
>assembled in the normal way.
I have a PowerPC based NAS device that was damaged by
a recent a brownout. The drives in the array are
fine, but the device's firmware was corrupted. My
first attempt to assemble the array on my x86 system
failed due to the endian differences. After applying
this patch, the mdadm examine command worked
perfectly. As of yet, I have not attempted to update
the superblocks. I would like to leave the original
superblocks intact so that I can reinstall the drives
in my NAS device when it is repaired. Is it possible
to assemble the array without overwriting the
superblocks?
-Brent
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
next reply other threads:[~2005-08-09 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 4:49 Brent Walsh [this message]
2005-08-09 4:57 ` endianness of Linux kernel RAID Neil Brown
2005-08-11 13:38 ` Brent Walsh
2005-08-18 4:44 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2005-08-03 12:07 Gregory Seidman
2005-08-03 13:05 ` Paul Clements
2005-08-03 15:36 ` Gregory Seidman
2005-08-03 15:51 ` Paul Clements
2005-08-03 18:50 ` Dan Stromberg
2005-08-04 5:14 ` Neil Brown
2005-08-04 6:47 ` Neil Brown
2005-08-04 7:20 ` Daniel Pittman
2005-08-04 11:40 ` Gregory Seidman
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=20050809044903.97593.qmail@web35308.mail.mud.yahoo.com \
--to=blinux_adm@yahoo.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).