[Bug 1088884] [NEW] no option to force --incremental (re)add to active array

[ceg]

Public bug reported:

The --incremental call (as also done by udev rules) refuses to (re)add a
temporarily disconnected members back to an already restarted (active)
raid array.

# mdadm --incremental /dev/sdb1
mdadm: not adding /dev/sdb1 to active array (without --run) /dev/md/0

# mdadm --incremental --run /dev/sdb1
mdadm: failed to add /dev/sdb1 to /dev/md/0: Invalid argument.

Even though this refusal may in the future only happen for true
conflicts (Bug #1088532), there is still an option missing to --force
the addition anyway.

Using --force with --incremental (where mdadm will still apply sanity
checks to not add it to a completely wrong array etc.) seems much less
dangerous than forcing the user to have to --zero-superblock around in
the system.

** Affects: mdadm (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

+ The --incremental (udev) call refuses to (re)add a temporarily
+ disconnected members back to an already restarted (active) raid.
  
- The --incremental (udev) call refuses to (re)add a temporarily disconnected members back to an already restarted (active) raid. 
+ # mdadm --incremental /dev/sdb1
+ mdadm: not adding /dev/sdb1 to active array (without --run) /dev/md/0
  
- Even though the refusal may in the future only happen for obvious
+ # mdadm --incremental --run /dev/sdb1
+ mdadm: failed to add /dev/sdb1 to /dev/md/0: Invalid argument.
+ 
+ Even though this refusal may in the future only happen for true
  conflicts (Bug #1088532), there is still an option missing to --force
  the addition anyway.
  
  Using --force with --incremental (where mdadm will still apply sanity
  checks to not add it to a completely wrong array etc.) seems much less
  dangerous than forcing the user to have to --zero-superblock around in
  the system.

** Description changed:

- The --incremental (udev) call refuses to (re)add a temporarily
- disconnected members back to an already restarted (active) raid.
+ The --incremental call (as also done by udev rules) refuses to (re)add a
+ temporarily disconnected members back to an already restarted (active)
+ raid array.
  
  # mdadm --incremental /dev/sdb1
  mdadm: not adding /dev/sdb1 to active array (without --run) /dev/md/0
  
  # mdadm --incremental --run /dev/sdb1
  mdadm: failed to add /dev/sdb1 to /dev/md/0: Invalid argument.
  
  Even though this refusal may in the future only happen for true
  conflicts (Bug #1088532), there is still an option missing to --force
  the addition anyway.
  
  Using --force with --incremental (where mdadm will still apply sanity
  checks to not add it to a completely wrong array etc.) seems much less
  dangerous than forcing the user to have to --zero-superblock around in
  the system.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1088884

Title:
  no option to force --incremental (re)add to active array

Status in “mdadm” package in Ubuntu:
  New

Bug description:
  The --incremental call (as also done by udev rules) refuses to (re)add
  a temporarily disconnected members back to an already restarted
  (active) raid array.

  # mdadm --incremental /dev/sdb1
  mdadm: not adding /dev/sdb1 to active array (without --run) /dev/md/0

  # mdadm --incremental --run /dev/sdb1
  mdadm: failed to add /dev/sdb1 to /dev/md/0: Invalid argument.

  Even though this refusal may in the future only happen for true
  conflicts (Bug #1088532), there is still an option missing to --force
  the addition anyway.

  Using --force with --incremental (where mdadm will still apply sanity
  checks to not add it to a completely wrong array etc.) seems much less
  dangerous than forcing the user to have to --zero-superblock around in
  the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1088884/+subscriptions