From: Trevor Cordes <trevor@tecnopolis.ca>
To: NeilBrown <neilb@suse.com>
Cc: Continuation of Round Table discussion <roundtable@muug.ca>,
Adam Thompson <athompso@athompso.net>,
linux-raid@vger.kernel.org
Subject: Re: [RndTbl] Big-endian RAID5 recovery problem
Date: Sat, 6 May 2017 01:41:17 -0500 [thread overview]
Message-ID: <20170506014117.4d3f1689@pog.tecnopolis.ca> (raw)
In-Reply-To: <87fugio7cy.fsf@notabene.neil.brown.name>
On 2017-05-06 NeilBrown wrote:
> On Mon, May 01 2017, Adam Thompson wrote:
>
> > The problem is that the disks use the v0.90 metadata format, and
> > they came from a big-endian system, not a little-endian system. MD
> > superblocks *since* v0.90 are endian-agnostic, but back in v0.90,
> > the superblock was byte-order specific.
>
> Look for "--update=byteorder" in the mdadm man page.
Doh! Make that double-doh! So easy, yet so hidden. I'll request one
little tweak/feature: can the man page be updated so that that option
has the word "endian" somewhere in its description? I think most of us
did as the first attempt at helping: man mdadm, search endian. When
that failed, no one thought to search byteorder! Even google didn't
fix that one, at least not for my web searches.
Thanks linux-RAID guys (especially Neil), once again you make the
difficult easy.
next prev parent reply other threads:[~2017-05-06 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 21:39 Big-endian RAID5 recovery problem Adam Thompson
2017-05-01 21:59 ` Anthony Youngman
2017-05-01 22:33 ` Adam Thompson
2017-05-02 2:47 ` Phil Turmel
2017-05-02 7:29 ` [RndTbl] " Trevor Cordes
2017-05-02 8:59 ` Roman Mamedov
2017-05-05 19:22 ` [RndTbl] " Adam Thompson
2017-05-06 5:57 ` NeilBrown
2017-05-06 6:41 ` Trevor Cordes [this message]
2017-05-07 23:40 ` [mdadm PATCH] Mention "endian" in documentation for --update=byte-order NeilBrown
2017-05-08 17:42 ` Jes Sorensen
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=20170506014117.4d3f1689@pog.tecnopolis.ca \
--to=trevor@tecnopolis.ca \
--cc=athompso@athompso.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=roundtable@muug.ca \
/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).