linux.git/drivers/block/drbd/drbd_actlog.c, branch v3.7

drbd: announce FLUSH/FUA capability to upper layers

2012-07-24T13:14:28+00:00

Unconditionally announce FLUSH/FUA to upper layers.
If the lower layers on either node do not actually support this,
generic_make_request() will deal with it.

If this causes performance regressions on your setup,
make sure there are no volatile caches involved,
and mount -o nobarrier or equivalent.

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

drbd: differentiate between normal and forced detach

2012-07-24T12:06:18+00:00

Aborting local requests (not waiting for completion from the lower level
disk) is dangerous: if the master bio has been completed to upper
layers, data pages may be re-used for other things already.
If local IO is still pending and later completes,
this may cause crashes or corrupt unrelated data.

Only abort local IO if explicitly requested.
Intended use case is a lower level device that turned into a tarpit,
not completing io requests, not even doing error completion.

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

drbd: introduce a bio_set to allocate housekeeping bios from

2012-05-09T13:17:07+00:00

Don't rely on availability of bios from the global fs_bio_set,
we should use our own bio_set for meta data IO.

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

drbd: missing wakeup after drbd_rs_del_all

2012-05-09T13:16:42+00:00

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

drbd: Consider the disk-timeout also for meta-data IO operations

2012-05-09T13:16:30+00:00

If the backing device is already frozen during attach, we failed
to recognize that. The current disk-timeout code works on top
of the drbd_request objects. During attach we do not allow IO
and therefore never generate a drbd_request object but block
before that in drbd_make_request().

This patch adds the timeout to all drbd_md_sync_page_io().

Before this patch we used to go from D_ATTACHING directly
to D_DISKLESS if IO failed during attach. We can no longer
do this since we have to stay in D_FAILED until all IO
ops issued to the backing device returned.

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

drbd: fix potential spinlock deadlock

2012-05-09T13:15:58+00:00

drbd_try_clear_on_disk_bm() has a sanity check for the number of blocks
left to be resynced (rs_left) in the current resync extent.
If it detects a mismatch, it complains, and forces a disconnect using
drbd_force_state(mdev, NS(conn, C_DISCONNECTING));

Unfortunately, this may be called while holding the req_lock,
and drbd_force_state() want's to aquire that lock itself. Deadlock.

Don't force a disconnect, but fix up rs_left by recounting and
reassigning the number of dirty blocks in that extent.

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

drbd: Hold a reference to ldev while doing meta-data IO

2012-05-09T08:31:11+00:00

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

drbd: Keep a reference to the bio until the completion handler finished

2012-05-09T08:28:51+00:00

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

drbd: Implemented wait_until_done_or_disk_failure()

2012-05-09T08:26:51+00:00

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

drbd: Replaced md_io_mutex by an atomic: md_io_in_use

2012-05-09T08:22:31+00:00

The new function drbd_md_get_buffer() aborts waiting for the buffer
in case the disk failes in the meantime.

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