[PATCH] md: Fix data corruption when a degraded raid5 array is reshaped.

This patch fixes a fairly serious bug in md/raid5 in 2.6.23 and 24-rc. It would be great if it cold get into 23.13 and 24.final. Thanks. NeilBrown ### Comments for Changeset We currently do not wait for the block from the missing device to be computed from parity before copying data to the new

Re: [PATCH] md: Fix data corruption when a degraded raid5 array is reshaped.

On Thu, 2008-01-03 at 15:46 -0700, NeilBrown wrote: This patch fixes a fairly serious bug in md/raid5 in 2.6.23 and 24-rc. It would be great if it cold get into 23.13 and 24.final. Thanks. NeilBrown ### Comments for Changeset We currently do not wait for the block from the missing device

Re: [PATCH] md: Fix data corruption when a degraded raid5 array is reshaped.

On Thu, 2008-01-03 at 16:00 -0700, Williams, Dan J wrote: On Thu, 2008-01-03 at 15:46 -0700, NeilBrown wrote: This patch fixes a fairly serious bug in md/raid5 in 2.6.23 and 24-rc. It would be great if it cold get into 23.13 and 24.final. Thanks. NeilBrown ### Comments for Changeset

Re: [PATCH] md: Fix data corruption when a degraded raid5 array is reshaped.

On Thursday January 3, [EMAIL PROTECTED] wrote: On closer look the safer test is: !test_bit(STRIPE_OP_COMPUTE_BLK, sh-ops.pending). The 'req_compute' field only indicates that a 'compute_block' operation was requested during this pass through handle_stripe so that we can issue a