Neil Brown wrote:
> > How do I force MD to raise the event counter on sdb1 and accept it
> > into the array as-is, so I can avoid bad-block induced data
> > corruption?
>
> For that, you have to recreate the array.
Scary. And hairy.
How much do I have to bribe you to make this work:
# mdadm --assemble /dev/md1 --force /dev/sd{a,b,c,d,e,f}1
Not now, that is, but for the sake of future generations? :)
> Make sure you get the
> chunksize, parity algorithm, and order correct, but something like
>
> mdadm -C /dev/md1 --assume-clean /dev/sda1 /dev/sdb1 /dev/sdc1 \
> /dev/sdd1 /dev/sde1 /dev/sdf1
How do I backup the MD superblocks first so I can 'dd'-restore them in
case the above command totally wrecks the array because I got it
wrong?
It's an old array, so it's version 00.90.00 superblocks - does that
make a difference?
> and then
> echo check > /sys/block/md1/md/sync_action
>
> and see what
> cat /sys/block/md1/md/mismatch_count
> reports at the end.
> Then maybe 'echo repair > ....'
Super, thanks as always for your kind help.
(After examining the syslog, I think that there might be a bug, or not
- I'll start a new thread about that.)
-
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
