Re: behavior different from mdadm 2.6.4 and 3.0?

On Monday December 15, jnelson-linux-raid@jamponi.net wrote:

mdadm --incremental seems to behave differently for me between mdadm
2.6.4 and 3.0

With 2.6.4, mdadm --incremental /dev/nbd0 does this:

mdadm: /dev/nbd0 attached to /dev/md10 which is already active.

With 3.0, it does this:

mdadm: /dev/md10 is already in use.

and does *not* add it to the array.

Sounds like /var/run/mdadm/map is not correctly up-to-date.
Does running
   mdadm -Ir

make "mdadm -I /dev/nbd0" work properly again?

Can you provide a sequence of steps which leads to the error message
that you report?

Thanks,
NeilBrown