From: jeffs_linux@123mail.org
To: Luca Berra <bluca@comedia.it>, linux-raid@vger.kernel.org
Subject: Re: Bug or not? Same array reports different/transformed UUID depending on check-method used.
Date: Tue, 21 Jun 2011 05:50:49 -0700 [thread overview]
Message-ID: <1308660649.16501.1465562409@webmail.messagingengine.com> (raw)
In-Reply-To: <20110621054258.GA22391@maude.comedia.it>
On Tue, 21 Jun 2011 07:42 +0200, "Luca Berra" <bluca@comedia.it> wrote:
> The map_file, on the contrary, is always read and written as 4 32bit
> values in host endian order, so on x86 machines you will find it
> swapped.
>
> Summary: the mapfile is for mdadm internal use only, use mdadm commands
> (--detail, --examine) to obtain data.
>
> (*) http://en.wikipedia.org/wiki/Endianness
Ok.
How might that explain that one array IS 'swapped', and the other is
not? They're both on the same machine?
jeff
prev parent reply other threads:[~2011-06-21 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 16:29 Bug or not? Same array reports different/transformed UUID depending on check-method used jeffs_linux
2011-06-21 5:42 ` Luca Berra
2011-06-21 12:50 ` jeffs_linux [this message]
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=1308660649.16501.1465562409@webmail.messagingengine.com \
--to=jeffs_linux@123mail.org \
--cc=bluca@comedia.it \
--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).