linux/drivers/block/drbd/drbd_strings.c, branch v3.0.6Linux kernel source treehttps://git.amat.us/linux/atom/drivers/block/drbd/drbd_strings.c?h=v3.0.62011-03-10T10:36:18Zdrbd: Rename enum drbd_state_ret_codes to enum drbd_state_rv2011-03-10T10:36:18ZAndreas Gruenbacheragruen@linbit.com2010-12-08T00:06:16Zurn:sha1:c8b325632f0e5ffdaeca3d1f3be77c9399316a40
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
drbd: Implemented two new connection states Ahead/Behind2011-03-10T10:34:46ZPhilipp Reisnerphilipp.reisner@linbit.com2010-10-27T10:21:30Zurn:sha1:67531718d8f1259f01ab84c2aa25f7b03c7afd46
In this connection mode, the ahead node no longer replicates
application IO. The behind's disk becomes out dated.
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
drbd: don't start a resync without access to up-to-date Data2010-05-17T23:08:18ZLars Ellenberglars.ellenberg@linbit.com2010-04-01T14:59:32Zurn:sha1:8d4ce82b3ccd755c8ba401469ced5286b1e02284
In case both nodes are "inconsistent", invalidate would
have started a resync anyways, without a chance to ever
succeed, just filling the logs with warning messages.
Simply disallow that state change,
re-using the SS_NO_UP_TO_DATE_DISK return value.
This also changes the corresponding error string to
"Need access to UpToDate Data" -- I found the
"Refusing to be Primary without at least one UpToDate disk"
answer misleading in some situations anyways.
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
The DRBD driver2009-10-01T19:17:49ZPhilipp Reisnerphilipp.reisner@linbit.com2009-09-25T23:07:19Zurn:sha1:b411b3637fa71fce9cf2acf0639009500f5892fe
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>