behavior different from mdadm 2.6.4 and 3.0?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux