On Mon, 19 Mar 2012 10:58:57 +0100 Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
wrote:
> Hi,
>
> Please is there a way to update a homehost value for a specific raid
> component?
>
> md7 is raid1 composed of md5 and md6. UUID of md7 is listed in mdadm.conf:
>
> ARRAY /dev/md7 level=raid1 num-devices=2 metadata=01.00
> UUID=dde16cd5:2e17c743:fcc7926c:fcf5081e
>
>
> Every time I reboot, md7 is auto assembled only from md5. When running
> manually, I get
>
> mdadm --verbose -A /dev/md7 --scan
> ...
> mdadm: /dev/md6 misses out due to wrong homehost
> ...
>
There is something very strange here.
md5 and md6 look to some extent like different parts of the same RAID1.
They have the same Array UUID, the same "Update Time" and the same "Events"
counter.
However they have different "Creation Time" (19/Jan/2011 vs 17/Jun/2010) and
different names ("orfeus:7" vs "'orpheus':7").
I cannot imagine how that would happen.
mdadm notices they are different so it cannot use them both. It chooses md5
over md6 as md5 has the 'correct' homehost name.
Your best bet would be to re-create the array so it gets good clean metadata.
mdadm -S /dev/md7
mdadm -C /dev/md7 -l1 -n2 --assume-clean --metadata=1.0 /dev/md6 /dev/md5
should do it. If you want to keep the same uuid, add
--uuid=dde16cd5:2e17c743:fcc7926c:fcf5081e
to that command.
--update=homehost only works when assembling, and updates the homehost for
all members of the array. The would work if the create times were the same,
but a they are different, mdadm thinks they are different arrays.
NeilBrown
>
> Indeed, all the raid components (there are many more belonging to
> different raids on my machine) list the "local to host orfeus" homehost,
> such as:
>
> orfeus:~# mdadm --examine /dev/md5
> /dev/md5:
> Magic : a92b4efc
> Version : 1.0
> Feature Map : 0x0
> Array UUID : dde16cd5:2e17c743:fcc7926c:fcf5081e
> Name : orfeus:7 (local to host orfeus)
> Creation Time : Wed Jan 19 21:36:19 2011
> Raid Level : raid1
> Raid Devices : 2
>
> Avail Dev Size : 4356361184 (2077.27 GiB 2230.46 GB)
> Array Size : 4356361184 (2077.27 GiB 2230.46 GB)
> Super Offset : 4356361440 sectors
> State : clean
> Device UUID : a4973bb6:2cd83805:ba441193:56321f9b
>
> Update Time : Mon Mar 19 02:36:33 2012
> Checksum : 7b8eeffd - correct
> Events : 11853346
>
>
> Device Role : Active device 1
> Array State : AA ('A' == active, '.' == missing)
>
>
> While the md6 has the homehost different:
> orfeus:~# mdadm --examine /dev/md6
> /dev/md6:
> Magic : a92b4efc
> Version : 1.0
> Feature Map : 0x0
> Array UUID : dde16cd5:2e17c743:fcc7926c:fcf5081e
> Name : 'orfeus':7
> Creation Time : Thu Jun 17 22:51:47 2010
> Raid Level : raid1
> Raid Devices : 2
>
> Avail Dev Size : 4356361184 (2077.27 GiB 2230.46 GB)
> Array Size : 4356361184 (2077.27 GiB 2230.46 GB)
> Super Offset : 4356361440 sectors
> State : clean
> Device UUID : 9144c9ad:8ee3ed37:69b53956:03bebdd6
>
> Update Time : Mon Mar 19 02:36:33 2012
> Checksum : 94c11ff3 - correct
> Events : 11853346
>
>
> Device Role : Active device 0
> Array State : AA ('A' == active, '.' == missing)
>
>
> There is no "local to host orfeus" in homehost of md6. Otherwise, the
> array UUID fits that of md7. It was added after last reboot when the
> array failed to assemble automatically.
>
> Following the man page, I tried running
>
> mdadm --verbose -A /dev/md7 --update=homehost --scan
>
> with no difference. Unfortunately I was not able to find how to change
> the homehost of md6 to be local to orfeus. I do not want to force adding
> md6 to the array and go through the whole rebuild since the data
> themselves are OK.
>
>
> Thanks a lot for any hints and help.
>
> Best regards,
>
>
> Pavel.
> --
> 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
Attachment:
signature.asc
Description: PGP signature
