1. 10 3月, 2011 23 次提交
  2. 28 11月, 2010 1 次提交
  3. 18 11月, 2010 1 次提交
  4. 23 10月, 2010 1 次提交
  5. 22 10月, 2010 2 次提交
    • L
      drbd: fix potential data divergence after multiple failures · 6719fb03
      Lars Ellenberg 提交于
      If we get an IO-error during an activity log transaction,
      if we failed to write the bitmap of the evicted extent,
      we must not write the transaction itself.
      If we failed to write the transaction,
      we must not even submit the corresponding bio,
      as its extent is not yet marked in the activity log.
      
      Otherwise, if this was a disconneted Primary (degraded cluster), which
      now lost its disk as well, and we later re-attach the same backend
      storage, we possibly "forget" to resync some parts of the disk that
      potentially have been changed.
      
      On the receiving side, when receiving from a peer with unhealthy disk,
      checking for pdsk == D_DISKLESS is not enough, we need to set out of
      sync and do AL transactions for everything pdsk < D_INCONSISTENT on the
      receiving side.
      Signed-off-by: NPhilipp Reisner <philipp.reisner@linbit.com>
      Signed-off-by: NLars Ellenberg <lars.ellenberg@linbit.com>
      6719fb03
    • L
      drbd: fix potential deadlock on detach · 82f59cc6
      Lars Ellenberg 提交于
      If we have contention in drbd_al_begin_iod (heavy randon IO),
      an administrative request to detach the disk may deadlock
      for similar reasons as the recently fixed deadlock if detaching
      because of IO-error.
      
      The approach taken here is to either go through the intermediate
      cleanup state D_FAILED, or first lock out application io,
      don't just go directly to D_DISKLESS.
      
      We need an additional state bit (WAS_IO_ERROR) to distinguish
      the -> D_FAILED because of IO-error from other failures.
      
      Sanitize D_ATTACHING -> D_FAILED to D_ATTACHING -> D_DISKLESS.
      If only attaching, ldev may be missing still, but would be referenced
      from within the after_state_ch for -> D_FAILED, potentially
      dereferencing a NULL pointer.
      Signed-off-by: NPhilipp Reisner <philipp.reisner@linbit.com>
      Signed-off-by: NLars Ellenberg <lars.ellenberg@linbit.com>
      82f59cc6
  6. 15 10月, 2010 12 次提交