-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jun 19, 2005, at 5:05 PM, Paul Clements wrote:
Aaron Botsis wrote:
Is this a bug? Is just the magic number whacked? or are the
superblock data structures too?
The version 0.90 superblock is not "endian agnostic". It records
data in whatever endian order the host machine is (Version 1
superblocks, by the way, fix this, but are not available unless you
have the latest 2.6 kernel and mdadm).
So it's really only the superblock, then? Does that mean the parity
stripes don't suffer from endian problems as well?
what's the best way to fix this?
Unfortunately, I don't think there's an easy way. But, if you can
get the array back up on the original machine and copy down all the
information (or if you already have it) then you can re-create the
array on the x86 machine using "mdadm -C", but be careful... :)
By information, I'm assuming you mean chunk size, parity algo, etc?
So I can just whack a new superblock on top and all will be well
because the parity stripes will be cool?
what's what look like:
mdadm -C -c bleh -level=5 --parity=left --raid-devices=3 /dev/md0 /
dev/hda1 /dev/hdb1 /dev/hdc1
??
Also, I thought I noticed the array in degraded mode (probably a
failed read or something) before the machine it was in crashed...
(bad root disk) if I do this, will BadThings(tm) occur??
If so, can I just hack mdadm to fixup the order while reading the
superblock, and recreate in degraded based on that?
Thanks again for the help.
- -Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCti/xN/nDplnlBBgRAuKIAKCNqiuC6+0NBUCQMFDxW7gMTnk8/ACfdHQ2
hSmINmk+Hq0v1QdZ+4teLRc=
=eBtc
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
