behavior different from mdadm 2.6.4 and 3.0?

Started by Jon Nelson on Dec 15, 2008

open the first message on its own page

Message details and related content
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.

-- 
Jon
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help