lp:drbd8
- Get this branch:
- bzr branch lp:drbd8
Branch merges
Import details
This branch is an import of the HEAD branch of the Git repository at https://github.com/LINBIT/drbd-8.4.git.
Last successful import was .
Recent revisions
- 5167. By Roland Kammerer
-
ship public part of the kernel module signing key
We will sign our ko files soon. ship the public in the RHEL rpm package.
- 5166. By Dan Carpenter <email address hidden>
-
block: drbd: remove a stay unlock in __drbd_
send_protocol( ) There are two callers of this function and they both unlock the mutex so
this ends up being a double unlock.Fixes: 44ed167da748 ("drbd: rcu_read_lock() and rcu_dereference() for tconn->net_conf")
Signed-off-by: Dan Carpenter <email address hidden>
Signed-off-by: Philipp Reisner <email address hidden> - 5165. By Lars Ellenberg <email address hidden>
-
drbd: set BDI_CAP_
STABLE_ WRITES, we want page content to NOT change during write-out When the feature was introduced, it was made "default".
But then it soon was changed to "opt-in", which we apparently missed. - 5164. By Roland Kammerer
-
double DRBD_RESYNC_
RATE_MAX There has been a customer that reached the limit. Blindly double it.
Signed-off-by: Roland Kammerer <email address hidden>
- 5162. By Lars Ellenberg <email address hidden>
-
drbd: skip spurious timeout (ping-timeo) when failing promote
If you try to promote a Secondary while connected to a Primary
and allow-two-primaries is NOT set, we will wait for "ping-timeout"
to give this node a chance to detect a dead primary,
in case the cluster manager noticed faster than we did.But if we then are *still* connected to a Primary,
we fail (after an additional timeout of ping-timout).This change skips the spurious second timeout.
Most people won't notice really,
since "ping-timeout" by default is half a second.But in some installations, ping-timeout may be 10 or 20 seconds or more,
and spuriously delaying the error return becomes annoying. - 5161. By Lars Ellenberg <email address hidden>
-
drbd: don't retry connection if peers do not agree on "authentication" settings
emma: "Unexpected data packet AuthChallenge (0x0010)"
ava: "expected AuthChallenge packet, received: ReportProtocol (0x000b)"
"Authentication of peer failed, trying again." Pattern repeats.
There is no point in retrying the handshake,
if we expect to receive an AuthChallenge,
but the peer is not even configured to expect or use a shared secret. - 5160. By Luc Van Oostenryck <email address hidden>
-
drbd: fix print_st_err()'s prototype to match the definition
print_st_err() is defined with its 4th argument taking an
'enum drbd_state_rv' but its prototype use an int for it.Fix this by using 'enum drbd_state_rv' in the prototype too.
Signed-off-by: Luc Van Oostenryck <email address hidden>
Signed-off-by: Roland Kammerer <email address hidden>
Signed-off-by: Lars Ellenberg <email address hidden>
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)