linux.git/drivers/block/drbd/drbd_req.c, branch v2.6.38

drbd: Removed checks for REQ_HARDBARRIER on incomming BIOs

2010-10-23T11:02:34+00:00

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: Silenced an assert

2010-10-22T13:55:22+00:00

That assertion's condition needed adjustment for today's semantics

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: rate limit an error message

2010-10-22T13:53:10+00:00

If we don't rate limit it, and you happen to log err level messages via
serial console, an IO error on a disconnected Primary may cause serious
unresponsiveness.

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: fix potential data divergence after multiple failures

2010-10-22T13:50:27+00:00

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: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: Track the reasons to suspend IO in dedicated state bits

2010-10-14T16:38:40+00:00

There are three ways to get IO suspended:

 * Loss of any access to data
 * Fence-peer-handler running
 * User requested to suspend IO

Track those in different bits, so that one condition clearing its
state bit does not interfere with the other two conditions.

Only when the user resumes IO he overrules all three bits.

The fact is hidden from the user, he sees only a single suspend
bit.

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: Disable activity log updates when the whole device is out of sync

2010-10-14T16:38:26+00:00

When the complete device is marked as out of sync, we can disable
updates of the on disk AL. Currently AL updates are only disabled
if one uses the "invalidate-remote" command on an unconnected,
primary device, or when at attach time all bits in the bitmap are
set.

As of now, AL updated do not get disabled when a all bits becomes
set due to application writes to an unconnected DRBD device.
While this is a missing feature, it is not considered important,
and might get added later.

BTW, after initializing a "one legged" DRBD device
drbdadm create-md resX
drbdadm -- --force primary resX
AL updates also get disabled, until the first connect.

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: fix list corruption (recent regression)

2010-10-14T16:31:43+00:00

The commit 288f422ec13667de40b278535d2a5fb5c77352c4
 drbd: Track all IO requests on the TL, not writes only
moved a list_add_tail(req, ) into a region where req
may have just been freed due to conflict detection.

Fix this by adding a proper cleanup section for that code path.

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: Allow tl_restart() to do IO completion while IO is suspended

2010-10-14T13:05:08+00:00

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: Ensure that the peer was not rebootet in the meantime before resending TL

2010-10-14T13:01:37+00:00

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg

drbd: Do not allow a fencing-policy of resource-and-stonith with protocol A

2010-10-14T12:53:42+00:00

Signed-off-by: Philipp Reisner 
Signed-off-by: Lars Ellenberg