On Monday February 9, jnelson-linux-raid@xxxxxxxxxxx wrote: > > > > The typical use case for me is this: I will run the array (/dev/md11) in > degraded mode (without /dev/nbd0) for a week or so. > At some point, I will try to synchronize the underlying devices. To do this > I use: > > mdadm /dev/md11 --re-add /dev/nbd0 > > The issues I encounter are this: the array goes into *recovery* mode rather > than *resync*, despite the fact that /dev/nbd0 was at one point a full > member (in sync) of the array. Typically, less than 1/3 of the array needs > to be resynchronized, often much less than that. I've managed to reproduce this. If you fail the write-mostly device when the array is 'clean' (as reported by --examine), it works as expected. If you fail it when the array is 'active', you get the full recovery. The array is 'active' if there have been any writes in the last 200 msecs, and clean otherwise. I'll have to have a bit of a think about this and figure out where what the correct fix is. Nag me if you haven't heard anything by the end of the week. Thanks, NeilBrown -- 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
