repeating the process on another box, i just noticed that these two
results' UUIDs match exactly,
/dev/.mdadm/map /dev/md/0_0 52f5b43c:e83f7e2a:be6ad32e:0536ab0e
mdadm --detail --scan /dev/md/0_0 52f5b43c:e83f7e2a:be6ad32e:0536ab0e
but the OTHER array's two UUIDs
/dev/.mdadm/map /dev/md127 79fb7ad4:289bfae5:86c535ff:202960f2
mdadm --detail --scan /dev/md127 d47afb79:e5fa9b28:ff35c586:f2602920
are 'transforms' of one another; e.g.,
mdadm --detail --scan /dev/md127 d47afb79:e5fa9b28:ff35c586:f2602920
d4 e5
7a fa
fb 9b
79: 28:...
|
| couplet order transform
|
d4 e5
7a fa
fb 9b
79: 28: ...
/dev/.mdadm/map /dev/md127 79fb7ad4:289bfae5:86c535ff:202960f2
what's happening here? that can't be a coincidence.
is this a bug? or maybe an artifact of the type of array?
jeff
--
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
