drbd-9.0.29~0+git.9a7bc817-3.3.1 >  A a'Np9|oX`!HN+!5wZev/*żJƓ79?qA) QH:4`I y*TշKm5D4Xcjo7܆x1̑*0Ʒ@X*`-Ka.♾UB!EKXRrd#]''ʎ)uSC\ RB:5KV#52827a91639de439a83953977bf862d555778d6cb0655385285fdb160b6ee4adc79c0a7f98918b6ec65da6a34b8c7b9baf6fa5574ۀa'Np9|HekY*a&X t`g߂^g ^hp@WrR1t-pjB7\eN̄,Br-| ;Ym"%HL&{Iޟ[itIs6DGkޕSٚ`d Aț׫vqV4we7m1 gbdX\~zc;, 6>"o*oiN&$!m:Af,=7}o*\\ݍ|~X>p??d # ^ $,0Ij{      ,D(8;9;:j;BGHIXYZ[ \8]L^obcde flu$v8PT_hlrCdrbd9.0.29~0+git.9a7bc8173.3.1Linux driver for the "Distributed Replicated Block Device"DRBD is a distributed replicated block device. It mirrors a block device over the network to another machine. Think of it as networked raid 1. It is a building block for setting up clusters.a'Ngoat16SUSE Linux Enterprise 15SUSE LLC GPL-2.0-or-laterhttps://www.suse.com/Unspecifiedhttps://drbd.linbit.com/linuxx86_64FFA큤A큤a'Na'N`Ja'N`J9f66086a7eaa4be35f8fb8e9a0b1fe1d7420e27bdf8863706b205596275d22fc1ca3e8f71b7de618968e7ea9fe47822d9e704dc476aef8544033abedec355225servicerootrootrootrootrootrootrootrootrootrootdrbd-9.0.29~0+git.9a7bc817-3.3.1.src.rpmdrbddrbd(x86-64)      drbd-utilsrpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)rpmlib(TildeInVersions)9.2.03.0.4-14.6.0-14.0-15.2-14.10.0-14.14.3`+_м@_j_F@_@_cO^@^@^g@^U @^,^]q]W]n]@]]w@]v>]1\"\@\73\U@[H[[U@ZZ@Z0@Zhu@Z'Z@YYp@YoIYA%@Y&@YX @XO@X@X8'X0>X X WXW@Vm@Vm@V\:@VO @V(V V7@UoU@UU0nwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comrbrown@suse.comnwang@suse.comnwang@suse.comnwang@suse.comjengelh@inai.denwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.combwiedemann@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comhare@suse.denwang@suse.comlpechacek@suse.comlpechacek@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comolaf@aepfle.denwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.comnwang@suse.com- bsc#1188472, update to 9.0.29 * fix data corruption when DRBD's backing disk is a degraded Linux software raid (MD) * add correct thawing of IO requests after IO was frozen due to loss of quorum * fix timeout detection after idle periods and for configs with ko-count when a disk on an a secondary stops delivering IO-completion events * fixed an issue where UUIDs where not shifted in the history slots; that caused false "unrelated data" events * fix switching resync sources by letting resync requests drain before issuing resync requests to the new source; before the fix, it could happen that the resync does not terminate since a late reply from the previous caused a out-of-sync bit set after the "scan point" * fix a temporal deadlock you could trigger when you exercise promotion races and mix some read-only openers into the test case * fix for bitmap-copy operation in a very specific and unlikely case where two nodes do a bitmap-based resync due to disk-states * fix size negotiation when combining nodes of different CPU architectures that have different page sizes * fix a very rare race where DRBD reported wrong magic in a header packet right after reconnecting * fix a case where DRBD ends up reporting unrelated data; it affected thinly allocated resources with a diskless node in a recreate from day0 event * speedup open() of drbd devices if promote has not chance to go through * new option "--reset-bitmap=no" for the invalidate and invalidate-remote commands; this allows to do a resync after online verify found differences * changes to socket buffer sizes get applied to established connections immediately; before it was applied after a re-connect * add exists events for path objects * forbid keyed hash algorithms for online verify, csyms and HMAC base alg * fix a regression introduces with 9.0.25; it failed to determine the right device size and the connection hangs in WFBitmapS/WFBitmapT repl state; to trigger this you need to do a partial resync to a new node with different backing device size * fix an issue with netlink packets processed in parallel on multiple CPUs; the bug caused drbdadm adjust failing in very rare cases * fix a very rare occurrence of a reconciliation resync getting stuck * fix a race condition that causes a detach operation to hang; it is very hard to trigger * fix a kernel OOPS (via a BUG()) upon adding a timer twice under very rare timing * fix a counter imbalance that could lead to assertion messages when a protocol A peer disconnects with a certain timing * fix a rare race with receiving bitmap and a state change while establishing a connection * fix UUID handling to avoid false split-brain detections; this bug got triggered an isolated primary that gets demoted, and temporal network interruptions among the remaining nodes * fix resync decision to obey disk states when the generation UUIDs are equal; the effect of this bug was that you could end up with two Outdated nodes after resync * fix concurrent disk-attach operations * Fix possible kernel warning regarding an inbalance of backing device link/unlink * move some amount of kernel backward compatibility code moved from the old method (drbd_wrappers.h) to new cocci semantic patches * add support renaming resources while its devices might be in use and process IO requests * Allow setting c_max_rate to 0 with the meaning that the resync controller has no upper limit for the resync speed * Fix regression: allow live migration between two diskful peers again * following upstream changes to DRBD up to Linux 5.12 and updated compat rules to support up to Linux 5.12 - Remove patch compat_blk_queue_stack_limits.patch Remove patch compat_get_fs.patch Remove patch compat_remove_kernel_setsockopt.patch Remove patch compat-test-header.patch Remove patch drbd-fix-zero-metadata-limit-by-page-size-misaligned.patch Remove patch remove_bdi_cap_stable_writes.patch Remove patch submit-bio-private-date.patch - Modify patch suse-coccinelle.patch - Add patch compat_genl_maxattr_in_ops.patch (48526a0f) - Bug fixes between 9.0.29 and 9.0.30 Add patch drbd-change-to-L_VERIFY_S-after-peer-is-L_VERIFY_T.patch Add patch drbd-Fix-abortion-of-a-connect-2-phase-commit.patch Add patch drbd-Fix-a-possible-NULL-deref-found-with-gcc-11-fan.patch Add patch drbd-Fix-locking-for-the-drbd_devices-idr.patch Add patch drbd-fix-protocol-compatibility-with-drbd-8.4-state.patch Add patch drbd-fix-race-condition-resetting-resync_next_bit.patch Add patch drbd-fix-termination-of-verify-with-stop-sector.patch Add patch drbd-remove-device_to_minor.patch Add patch drbd-use-DEFINE_MUTEX-insteadm-of-mutex_init.patch Add patch Revert-drbd-serialize-syncs-from-multiple-sources.patch - cocci apply: linux-5.12.0-2 queue_discard_zeroes_data__no_present (48920ff2a5a9)- bsc#1179708, compat to kernel v5.10 - Add patch compat_get_fs.patch Add patch remove_bdi_cap_stable_writes.patch- Update to 9.0.26 * fix a case of a disk unexpectedly becoming Outdated by moving the exchange of the initial packets into the body of the two-phase-commit that happens at a connect * fix adding of new volumes to resources with a primary node * reliably detect split brain situation on both nodes * fix an unexpected occurrence of NetworkFailure state in a tight drbdsetup disconnect; drbdsetup connect sequence * fix online verify to return to Established from VerifyS if the VerifyT node was temporarily Inconsistent during the run * fix a corner case where a node ends up Outdated after the crash and rejoin of a primary node * implement 'blockdev --setro' in DRBD * following upstream changes to DRBD up to Linux 5.9 and ensure compatibility with Linux 5.8 and 5.9 * fix a crash if during resync a discard operation fails on the resync-target node * fix online verify to not clamp disk states to UpToDate * fix promoting resync-target nodes; the problem was that it could modify the bitmap of an ongoing resync; which leads to alarming log messages * pause a resync if the sync-source node becomes inconsistent; an example is a cascading resync where the upstream resync aborts and leaves the sync-source node for the downstream resync with an inconsistent disk; note, the node at the end of the chain could still have an outdated disk (better than inconsistent) * allow force primary on a sync-target node by breaking the resync * minor fixes to the compat tests * fix for writes not getting mirrored over a connection while the primary transitions through the WFBitMapS state * completed missing logic of the new two-phase-commit based connect process; avoid connecting partitions with a primary in each; ensure consistent decisions if the connect attempt will be retried - Add patch compat-test-header.patch Add patch submit-bio-private-date.patch Add patch compat_remove_kernel_setsockopt.patch Add patch compat_blk_queue_stack_limits.patch - Remove patch rely-on-sb-handlers.patch (187bddac0) Remove patch fix-err-of-wrong-return-type.patch (969310232) Remove patch compat_generic_make_request.patch (8615d6837) Remove patch blk_alloc_queue_make_request.patch (edaa9b0f/fb59b40e) Remove patch remove_congested_fn_congested_data.patch (34484003/9b80d46b)- bsc#1178388, build error with -Wreturn-type Add patch fix-err-of-wrong-return-type.patch- bsc#1177417, kernel oops when submit bio Modify patch compat_generic_make_request.patch Modify patch blk_alloc_queue_make_request.patch - jsc#11801, remove is_opensuse macro for SLE15SP3 only, tumbleweed not support RT yet.- update to 9.0.25-0rc1 * fix a race condition between receiving UUIDs and finishing a resync that can lead to a false-positive split-brain detection later on * fix access after free of peer_req objects, that only happened when a resync target node is paused sync source at the same time * fix abortion of local state changes in case they can not proceed due to loss of connection * fix corner cases with reconciliation resync and parallel promote * fix an issue establishing a connection when the multipath feature is used to connect to a stacked resource without a dedicated service IP * fix sometimes a peer-disk state to another resync-target staying Outdated after two resyncs from the same sync source node finish * fix an (unlikely) deadlock while establishing a connection * deactivate the kref_debug code, it has performance implicatios * Introduce the "disconnected" hander; it receives the last connection state in the evnironment variable DRBD_CSTATE - Changes of drbd-9.0.24-1 * fix deadlock when connecting drbd-9 to drbd-8.4 and the drbd-9 side becomes sync-source * fix an issue with 3 (or more) node configurations; with a diskless node and two storage nodes; if one of the storage nodes was hard rebooted and came back and the diskless got primary and did not issue write requests and the returning storage node established a connection with the surviving storage node first, DRBD failed to upgrade the disk state to UpToDate after the resync * detect split-brain situations also when both nodes are primary; this is how it was in drbd-8.4; up to now drbd-9 did not realize the split-brain since it complains about the not allowed dual primary first; for this change a new protocol version was necessary * verified it compiles with Linux 5.7 - bsc#1176749, add compatible patches to SLE15 SP3 kernel. block layer api backport from kernel v5.9 Add patch blk_alloc_queue_make_request.patch Add patch compat_generic_make_request.patch Add patch remove_congested_fn_congested_data.patch- bsc#1172761, Update to drbd-9.0.23-1 * fix a deadlock (regression introduced in 9.0.22) that can happen when new current UUID is generated while a connection gets established * Do not create a new data generation if the node has 'allow-remote-read = no' set, is primary, and the local disk fails (because it has no access to good data anyome) * fix a deadlock (regression introduced in 9.0.22) that can be triggered if a minor is added into a resource with an established connection * generate new UUID immediately if a primary loses a disk due to an IO error * fix read requests on diskless nodes that hit a read error on a diskful node; the retry on another diskful node works, but a bug could lead to a log-storm on the diskless node * fix removal of diskless nodes from clusters with quorum enabled (initiated from the diskless itself) * fix wrongly declined state changes if connections are established concurrently * fix continuation of initial resync; before that the initial resync always started from the beginning if it was interrupted * use rwsem _non_owner() operations to avoid false positives of lock-dep when running on a debug kernel * fix a sometimes missed resync if only a diskless node was primary since the day0 UUID * fix a corner case where a SyncSource node does not recognise that a SyncTarget node declared the resync as finished * update compat up to Linux 5.6 - Remove patch without_pr_warning.patch since change in 7e6a20f7- jsc#11801, enable buildrt for Leap15.2 but Tumbleweed.- bsc#1166298, Update to drbd-9.0.22-1 * introduce locking to avoid connection retries when UUIDs or relevant flags change during the exchange of this data * improve serialization of events after loosing a primary * fix a constraint in sanitize state that can caused a promote to be deliced by some other node * fix a case of a false positive detection of a split brain condition * allow a resync target to switch to the resync source with less bits out of sync * fix bitmap UUID after resync to use current UUID from self rather than sync source * fix pushing bitmap UUID into history when changed * fix regression introduced with 9.0.20, that can cause a missed resync after a reconciliation resync * fix regression introduced with 9.0.20, that can cause a missed resync after a promote on a diskless node * fix UUID handling in case a node promotes during (a short) reconciliation resync * fix removing of a diskless node when quorum is enabled- Update to drbd-9.0.21-1, require coccinelle >= 1.0.8 * fix compat for write same on linux 4.9 and the Debian users * fix kernel compat for linux 4.8 and 4.9; this mainly affected Debian users; The symptoms where slow resync and resync getting stuck always at the same point * enable resync of lost and re-created backing devices (think lost node) when the backing device was thinly provisioned and its current uuid is pre-set to a 'day0 UUID' (by LINSTOR); that works by copying a unused bitmap slot which tracks all changes since day 0 * fix attach when bitmap is on PMEM; before it was set to 'all blocks out-of-sync' upon attach * avoid doing reconciliation resync multiple times by updating the resync target's dagtag after if completed successfully * return disk-state from Outdated to UpToDate when it loses connection while in WFBitMapT and we have a stable and UpToDate peer * new option --force-resync flag can be passed to new-current-uuid, that can be used to trigger initial resync without touching the role - Remove upstream drbd-update-resync-target-s-dagtag.patch - Modify patch suse-coccinelle.patch to adopt spaas- bsc#1159786, fix build issue against v5.5 add patch without_pr_warning.patch- bsc#1159333, back port patch for duplicate resync. add patch drbd-update-resync-target-s-dagtag.patch- bsc#1158446, fix metadata limit due to 64k page size of ppc64le. add patch drbd-fix-zero-metadata-limit-by-page-size-misaligned.patch- Remove obsolete Groups tag (fate#326485)- Update to drbd-9.0.20-1 * fix a case of false split brain detection if a diskless node promotes multiple times, by aligning the rules for generating a new current-UUID on a diskless nodes with them on a node with disk * check if we still have quorum by exchanging a drbd-ping with peers before creating new current UUID after loosing one peer * fix after weak handling to not interfere with reconciliation resyncs * retry connect when one of the relevant flags changes during UUID exchange * fix reconciliation resync if one of the secondary got an current-UUID update * fix resync to make progress after it was paused by an other resync operation * fix false split-brains when a resync source changes current-UUID during resync operation * fix restore of D_OUTDATED when the resource first only attached and then the peer objects are created (in contrast to the usual, new-peer, attach, connect) * abort creating new current-UUID when writing to meta-data fails in the moment where the new-current-UUID should be written * removed DRBD marking itself as read-only when secondary; this flag was exposed using the BLKROGET ioctl; that should be left to user-land use; recent KVM checks that flag, and does not dare auto-promote when set by DRBD * fix a small memory-leak when creating peer devices * fix a possible information leak of kernel memory that pads net-link packets * completing implications of "allow-remote-read=no"; i.e. when not to create a new-current-UUID as read-write access to the data set was lost; also fail both reads and writes if reads are no longer possible * new option value "rr-conflict=retry-connect"; that helps in scenarios with quorum where stopping a service takes longer than a temporarily network outage and DRBD's reconnect * code cleanups, introduced enums for remaining magic numbers * new kernel-backward-compatibility framework based on spatch/coccinelle, replacing an unmaintainable moloch of C preprocessor hell; Merged the complete kernel-compat submodule * ships with pre-computed compat-patches for main distros' kernels; in case an other kernel is found it tries to use local spatch, if that is not installed the build process tries to use a LINBIT hosted web service to create the compat patch ("spatch-as-a-service"). * compat with up to Linux-5.3-rc2 - Modify patch suse-coccinelle.patch to adopt spaas- bsc#1151579, fix collinelle default path and always trigger in obs Add patch suse-coccinelle.patch- bsc#1146117, disallow dual primaries when not configured. Modify patch rely-on-sb-handles.patch- Restore higher summary specifity. - Drop old-age %clean, %defattr.- bsc#1149945, update to 8e93a5d93 (drbd-9.0 branch) * Coccinelle support * compat with up to Linux-5.3 - Remove patch compat_no_bioset_initialized.patch- Update to 9.0.19-1 * check on CAP_SYS_ADMIN instead of CAP_NET_ADMIN for certain operations * fix detection of unstable resync * fix possible stuck resync when resync started from an other secondary and later continued from a primary * fix NULL dereference with disk-timeout enabled; was introduced in 9.0.9 * retry connect when own current UUID changes during UUID exchange * fix quorum tie-breaker diskless logic for settings other than "majority" * disable quorum tie-breaker for 0 voters * fix dax_direct_access() error return check * fix resync stuck at near completion; bug was intorduces with 9.0.17 * unblock IO when on-quorum-lost policy is changed (suspend -> io-error) * introduce allow-remote-read configuration option; set it to "no" for DR links you only want to write, but never read * only complain about UUID changes during initial handshake- Upgrade to 9.0.18-1 * Fix an IO deadlock under memory pressure * Fix disconnect timing in case the network connection suddenly drops all packets * Fix some misbehavior that surfaced with Ahead/Behind * Fix potential spinlock deadlock in IRQ * Minor fixes: forget-peer, _rcu iterators * Quickly stop resync during AHEAD/BEHIND by introducing new packet for that purpose. * The quorum feature can now use the connectivity to the majority of Diskless nodes as tiebreaker * Access meta-data using DAX if it is on persistent memory (NVDIMM or PMEM); For write intense workloads this is a x2 to x4 speedup! - Remove patch fix-make-error.patch since merged into upstream(46e8e3fc)- Upgrade to 9.0.17-1 * Fix UUID handling of a diskless primary that has not peer with usable data may not touch the current UUID * Fix resync-after dependencies; cross-resource dependencies and missing resources * Fix resync when the sync source suddenly connects to a more recent data set via an other connection and becomes sync target on that other connection; pause first resync; fix wrong display of negative resync progress percentage in this case * Fix volume numbers between 32767 and 65534 * Fix the data integrity implementation; it was broken since drbd-9.0 and reported only false positives * Fix for a corner-case when a promote action happens concurrently with a reconciliation resync * Improve resync code to be able to fully utilize fast storage backend devices and fast networks with resync traffic; as a side effect the settling time of the resync controller got shorter in for most cases * Show in the user-visible message who the opener is if if demote/down fails doe to someone holding a drbd device open * docker file for a "load drbd module container" and allow to disable user-mode-helpers, which is necessary for this container - Add patch fix-make-error.patch for build error of make against TW.- bsc#1118732, split brain handles malfunction when 2 primaries. - Add patch rely-on-sb-handlers.patch- bsc#1118841, kernel compatible issue. Have bioset_init but no bioset_initialized - Add patch compat_no_bioset_initialized.patch Remove patch compat_have_mempool_init.patch- bsc#1116820, kernel compatible issue of sle15sp1 - Add patch compat_have_mempool_init.patch- bsc#1115606, Update to 9.0.16-1 * Fix regression (introduced with 9.0.15) in handling request timeouts * Fix a possible distributed loop when establishing a connection * Fix a corner case in case a resync "overtakes" an other one * Fix clearing of the PRIMARY_LOST_QUORUM flag * Check peers before generating new current UUID after loosing a node * In case the locally configured address of a connection is not available keep on retrying until it comes back- Update to 9.0.15-1 * fix tracking of changes (on a secondary) against the lost disk of a primary and also fix re-attaching in case the disk is replaced * fix live migrate of VMs on DRBD when migrated to/from diskless nodes * fix an IO deadlock in DRBD when the activity log on a secondary runs full * fix hanging demote after IO error followed by attaching the disk again and the corresponding resync * fix DRBD dopping connection after an IO error on the secondary node * improve details when online changing devices from diskless to with disk and vice versa. (Including peers freeing bitmap slots) * new module parameter to disable support for older protocol versions * improve details when online changing devices from diskless to with disk * remove no longer relevant compat tests * expose openers via debugfs * optimize IO submit code path * compat for v4.18 kernel- Update to 9.0.14-1 * fix regression in 9.0.13: call after-split-brain-recovery handlers no auto-recovery strategies (not even the default: disconnect) would be applied, nodes would stay connected and all nodes would try to become the source of the resync. * fix spurious temporary promotion failure: if after Primary loss failover happened too quickly, transparently retry internally. * fixup recently introduced P_ZEROES to actually work as intended * fix online-verify to account for skipped blocks; otherwise, it won't notice that it has finished, apparently being stuck near "100% done" * expose more resync and online-verify statistics and details * improve accounting of "in-flight" data and resync requests * allow taking down an already useless minor device during "down", even if it is (temporarily) opened by for example udev scanning * fix for a node staying "only" Consistent and not returning to UpToDate in certain scenarios when fencing is enabled * fix data generation UUID propagate during resync * compat for upstream kernels up to v4.17- bsc#1090167, Update to 9.0.13-1 * abort a resync if a resync source becomes weakly and the sync targetis a neighbor of the primary * fix UUID handling with multiple diskless nodes * When a data-set gets into contact with an all diskless cluster, make sure to either set it to "Consistent" or reject the attach * correctly handle when a node that was marked as intentional diskless should get a disk * fix outdating of weakly connected nodes * made returning from Ahead to SyncSource more reliable * fix a hard to trigger deadlock in the receiver * fix online resize in the presence of two or more diskless nodes * fix online add of volumes to diskless nodes when it already has established connections * Set the SO_KEEPALIVE socket option on data sockets * automatically solve a specific split brain when quorum is enabled * Compat: Added support for kernels up to v4.15.x * new wire packet P_ZEROES a cousin of P_DISCARD, following the kernel as it introduced separated BIO ops for writing zeros and discarding * compat workaround for two RHEL 7.5 idiosyncrasies regarding refcount_t and struct nla_policy - Remove patch support-timer-setup.patch. Upstream fix 74b1cbb274- bsc#1080458, enable build with kernel-rt on x86_64. - bsc#1080459, support build against 4.15.0. setup_timer() change to timer_setup() - Add patch support-timer-setup.patch- bsc#1077318, Update to 9.0.12 * Fix a race condition in the device_open code path that can cause an internal counter to go negative - Update to 9.0.11 * Fix bug in compat code: Without this fix large bios are not split.- bsc#1074169, Update to 9.0.10-1 * Fix resync of two secondary nodes in the presence of a 3rd node that is primary (maybe with disk or diskless); Fixed the race condition that caused the resync to sometimes not terminate * Improve connection behavior with autopromote enable one node Primary and udev present. * Fix in memory alignment of DRBD's struct bio. * Improve the quorum implementation, so that is works nicely with for the purpose of replacing fencing with quorum in a Pacemaker setup. * Ensure compatibility with upstream Linux kernel 4.14 - Remove patch reproducible.patch- bsc#1068587, add build request libelf-devel to build.- bsc#1062749, disable buildrt against SLE15 x86_64 temporarily. This change will be removed when rt is ready.- bsc#1061981, update to 9.0.9 * fix occasionally forgotten resyncs in installations where diskless primaries are present. * fix an issue that causes unexpected split-brain upon connect. * in a cluster with a diskless primary, when a server goes away, and is not outdated, outdate it upon reconnect. * fix update of exposed data UUID on diskless primaries. * fix a possible OOPS when in a debug message regarding bitmap locking * fix discard bigger than 1MiB * fix left over bits in bitmap on SyncSource after resync * fix peers becoming unexpectedly displayed as D_OUTDATED at the end of a resync * fix a race between auto promote and auto demote of multiple volumes in a single resource * Speed up down of many resources by using call_rcu() instead of synchronize_rcu() * Make it compatible with the soon to be released 4.13 kernel - Modify reproducible.patch since part of the patch is merged- Add reproducible.patch to sort file lists (boo#1041090) and to override build date (boo#1047218) to fix build-compare- bsc#1045473, update to 9.0.8 fix a race condition between adding connections and receiving data fix a OOPS on a diskfull node when a request from a diskless node fix a distributed deadlock when doing a discard/write-same burst fix an issue with diskless nodes adopting wrong current UUIDs fix wrongly rejected two-phase-state transactions fix initial resync, triggered by "--force primary"(regression 9.0.7) Speed-up AL-updates with bio flags REQ_META and REQ_PRIO Merged changes from 8.4.10 and with that compatibility with Linux-4.12 - Remove patch fix-initial-sync-stop.patch - Fix the license to GPL-2.0+- bsc#1038852, fix initial sync not triggered add patch fix-initial-sync-stop.patch- Update to 9.0.7 Using 9.0.7rc2 for upgrading from rc1... - bsc#1028124, fix kernel compat - Fix a potenial split brain - Change the drbd-utils requirement to 8.9.11- Update to 9.0.7rc1 - various fixes to the 2-phase-commit online resize fix fencing and disk state trasition and from consistent, necessary for crm-fence-peer fix calculation of authoritative nodes Quorum to avoid data divergence, an alternative to fencing Compat with Linux 4.10 - Remove patch drbd_wrapper-Blank-out-WRITE_SYNC-warning-for-new-ke.patch - Add fix-resync-finished-with-syncs-have-bits-set.patch for bsc#1025089 - Including the compatible fix of bsc#1031299- Compability fixes for SLE12 SP3 (bsc#993388, FATE#321732) - Add patch drbd_wrapper-Blank-out-WRITE_SYNC-warning-for-new-ke.patch- bsc#1025585, upgrade to 9.0.6- Excluded openSUSE from RT KMP build (bsc#1005578)- Enabled RT KMP build (bsc#1005578)- bsc#1006176, compat with kernel 4.8 with 9.0.5- Upgrade 9.0.2 to 9.0.5 - Remove patch compat-4.7-9902af79-i_mutex.patch Remove patch compat-4.7-fe8fb75e-blk_queue_write_cache.patch Remove patch compat-4.7-50225243-kill-nla_put_u64.patch Remove patch compat-4.7-1dee3f59-align-nla-u64.patch Remove patch drbd-buildcompare.patch Remove patch kernel-4.5-compat.patch Remove patch temp.patch- bsc#983633, upgrade to ver9.0.2 to build against kernel 4.6/4.7 - Add patch compat-4.7-9902af79-i_mutex.patch - Add patch compat-4.7-fe8fb75e-blk_queue_write_cache.patch - Add patch compat-4.7-50225243-kill-nla_put_u64.patch - Add patch compat-4.7-1dee3f59-align-nla-u64.patch- Compat with kernel 4.5 - Add patch kernel-4.5-compat.patch- Remove timstamp from binaries Add patch drbd-buildcompare.patch- Update to release drbd-9.0.1 - Depend on drbd-utils >= 8.9.6- Update to released drbd-9.0.0 - Remove patch 0001-Support-zeroout-device-in-initial-sync.patch - Remove patch update-to-8.4.6-5.patch - Remove patch rename-GFP_WAIT-to-GFP_RECLAIM.patch - Remove patch new-bio-struct.patch- BSC#955968, support GFP_RECLAIM in kernel4.4 - Add rename-GFP_WAIT-to-GFP_RECLAIM.patch- BSC#950477, support new bio struct in kernel4.3 - Add new-bio-struct.patch- BSC#950477, update to 8.4.6-5 to fix bdi congested. - Rename 0001-drbd-Support-zeroout-device-in-initial-sync.patch to 0001-Support-zeroout-device-in-initial-sync.patch - Add update-to-8.4.6-5.patch- BSC#947460, add rcdrbd symlink.- Fate#317940, merge patch set into one patch. - Support zeroout/discard-devices instead of zap-devices - New feature flag FF_DISCARD - Add patch 0001-drbd-Support-zeroout-device-in-initial-sync.patch - Remove old patch set: Patch 0000-cover-letter-fate317940.patch Patch 0001-drbd-Fix-the-wrong-logic-of-moving-history.patch Patch 0002-drbd-Add-options-zap_devices-to-new-current-uuid.patch Patch 0003-drbd-A-function-to-zero-out-drbd-backing-device.patch Patch 0004-drbd-New-packet-P_ZERO_OUT.patch Patch 0005-drbd-Functions-to-notify-peer-node-to-start.patch Patch 0006-drbd-Wapper-for-zeroing-out-device-by-worker.patch Patch 0007-drbd-Flags-for-background-drbd-device-work.patch Patch 0008-drbd-Function-to-work-with-packet-P_ZERO_OUT.patch Patch 0009-drbd-Receive-zero-out-command-from-peer-node.patch Patch 0010-drbd-Handle-new-current-uuid-zap-devices.patch- BSC#939778. Add obsolete of old packages and a description for KMP package. - Require kernel-source-rt for RT.- Fate#317940. Speed up initial sync by supporting zero out device. Patch 0000-cover-letter-fate317940.patch Patch 0001-drbd-Fix-the-wrong-logic-of-moving-history.patch Patch 0002-drbd-Add-options-zap_devices-to-new-current-uuid.patch Patch 0003-drbd-A-function-to-zero-out-drbd-backing-device.patch Patch 0004-drbd-New-packet-P_ZERO_OUT.patch Patch 0005-drbd-Functions-to-notify-peer-node-to-start.patch Patch 0006-drbd-Wapper-for-zeroing-out-device-by-worker.patch Patch 0007-drbd-Flags-for-background-drbd-device-work.patch Patch 0008-drbd-Function-to-work-with-packet-P_ZERO_OUT.patch Patch 0009-drbd-Receive-zero-out-command-from-peer-node.patch Patch 0010-drbd-Handle-new-current-uuid-zap-devices.patch - Delete useless patch init-script-fixes.diff - ExcludeArch i586 and s390, since user space split into drbd-utils.- Update to 8.4.6 - With DRBD module version 8.4.5, we split out the management tools into their own repository. Started out as "drbd-utils version 8.9.0". To manage DRBD 8.4.5 kernel modules and above, want drbd-utils >= 8.9.0 - fix failing of user space helpers since kernel 3.13. This bug is known as 'out of mem, failed to invoke fence-peer helper' - fix connection timeouts for resources with multiple volumes - fix an issue with DRBD on linux software raid by properly remapping bi_bdev - fix a (hard to trigger) race condition between promoting to primary an connection handshake. In case the bug was hit the Primary got stuck in WFBitmapS connection state - Fix a NULL deref when resuming IO on a diskless primary - Fix compile issues with uncommon architectures - improvements to asender performance. With high end backing storage and networking equipment you may see IOPS improvements between 25% to 50%. - Highest number on a single drbd seen by LINBIT so far: 160000 IOPS - backport of events2 and status commands from drbd9. This allows to be DRBD9 compatible starting with this release, and to get used to DRBD9 compatible status reporting - support for lsblk in drbd - Update to 8.4.5 - fix potential BUG_ON in mempool_alloc for older kernels (<2.6.23) - fix cornercase of resync finished detection - fix drbd_ldev_destroy to run exactly once and in worker context - fix spurious detach/disconnect: don't announce WRITE_SAME - fix NULL pointer deref in blk_add_request_payload - (DISCARD/TRIM handling in sd) - fix regression: potential NULL pointer dereference - fix regression: potential list corruption - fix regression: potential deadlock in adm functions (drbdsetup) - fix regression: /sbin vs /usr/sbin in scripts - fix race stopping the worker thread - new debugfs presence expose oldest requests and other details - userspace moved to own repository - linux 3.13 and 3.14 compatibility - improve adaptive resync controler - reduce bitmap IO during resync - allow write-ordering policy to be bumped up again - trigger tcp_flush_pending_frames() for PING/PING_ACK - fix potential segfault in drbdadm adjust - drbdsetup improvements: fix netlink socket buffers; detect modprobe failuredrbd-kmp9.0.29~0+git.9a7bc817-3.3.19.0.29~0+git.9a7bc817-3.3.19.0.29~0+git.9a7bc817rcdrbddrbdChangeLogdrbdCOPYING/usr/sbin//usr/share/doc/packages//usr/share/doc/packages/drbd//usr/share/licenses//usr/share/licenses/drbd/-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.suse.de/SUSE:Maintenance:20953/SUSE_SLE-15-SP3_Update/4b70bf615c2392c0cb9f8031cb9a46d3-drbd.SUSE_SLE-15-SP3_Updatecpioxz5x86_64-suse-linuxdirectoryASCII textdrbd-utils9.2.0 utf-8abcb432b0c5875dcd0d631e8b9145d2b93f429a3c15556b946ef6f584ec64f2e?7zXZ !t/WJ]] cr$x#Ez/~M{E #o m/Չ2κ֑yݲuʛ*n|H)"IiGO cdQf }T_OprL[H^ͪ#`%%XcϬ} N O* ҩJ%#.,\cə3A㑴 Ep^7%vDK]J갺MzC wxj:V* ڀJmĆ#O ?^L,lũSx _>]FoWP ZUXx4Aj6G{zUg9X`ѧ_f7C DZ~2p_ۍ0L>^x&&YKӕB꒭Vp3Wy͇G*wP/[x@~vrKnHvwĨ,7Q eD(3#Dm0&[h@O])$ g$KgZwIf{Nhr#gW*aS&+S4dRlP5E9dN!<}z+?ltI0$}+VB?@hK 30GnDmօ ֻBP$ɶp6y|T{Fi,wz- o:&:+qr[JDrR͝;~(۵],xH]ى:ő'%؆L "T6ռN۷FϡrZv/[d6LMcԎŪУ!W2b<Va+'% [7{-$6hsDp.vlam,ïR`5X(=[huzhƢW)iݚ9ո9^d7Rg$ʭЛd G=EI rz4oUhu[KdnYrZKpxcIfĒCՂ=#1Jd+,ÁZ18:BM4٥d ~&Z=sEKuYi<DٝZ50'r?pQI-ƏTgS`\X/ƃf:ѹX|KY?0br3Bb145e 8Mޗ@)52?\WO >ˀg^|Ҫ1ys]̣cMܾ*H>qV]2Cն[L¼lT!C [(8򤪘1y\1Ev`L}j( p$A),KT$;J`̷.qޠF!j=ެHU $›K*:wԭQr:gb+z\Cml/菴=DS5t7Ү^Lk:Gc_-}I MDaPWNSXF##5:ɿA/o2.~Vm/&A l!Ř߆IF6b:v3NtM`R&6tBj[k"Sh.OKFlyh/zkמ|omR&Qy'P Da:ݹ$\+ ʯ>80K<#[X#lh"T˫,\ wOP= 6;*eh5 FC,qcO|-Be*'ܡ=_%6Imj)J$/LwE˾nJ6a1֩t( J İ[! 9B43] 4~ypm;XfQ 9Y 7 ?+wjtЬ^Ok|`&_2\S#&JdntP-yj7J&yo[0Oy%{mnv* <]Be[^WߌiicD7~o˓w8W6_{n1aq(g]oI5 =\2MRFr)vJR +ǘ [BpImWmkvf6:. UdYزoo߲X;YA-l$kFeݍvDn;X8&}O4ʔ=\ JJZPbej~8Z 7YPAС+\CٰE#*&UDb'M=y8'yjdWd)̘mhwڠg]T@5gBk,9|ыq8ZJ;*=[7yؾ\T; [Ia8" !ȘӎrW*2za’ R(95h=(hoުAwO%Ince. ծybq\wOzjjșts(SO5/a^_$ΌC-:0ΠnF!z{Z8(UCO3,+JAscEXشrw&̡9{lhF4u] ( Cߞ[.`_wX޳L:-ɆJ\??8/SH}*F$TL_s"TO'GP~5q#e|tDu4؃`b,V&ftSm},Db&MQ@e2RjL9HcEmSu -(^OLի 4֥^-:j>C5i@(.pL ]#z~/ղJ_[qo"&.A#M~H0 ~/s68>h+w8Z[ҟg}]N^Zbk0k32 nۆ.S83k4i{d3aAQh@4\4ƪ*2]>8/'LE&:Lr*3n}ѻU/6ڡA!C ew,]uNb%QYZs4Mo['uܙzOj`cuthk{3 '@*zQ g,O& Z@˭ɓn"j3|$Ywe7'U.&w/1dR ܧCh8xު=[W/_JP3<2PXcSj7~t#1FKUHL҆|yuڀGǏ;<λ3/غ NA_n4%؍_@i32\O`HMp$}wC?J/X Tǔ}?(ѯx NDO"!P%BQ~HcDL:E{|1{C+Q5оe=mgeUb< >rU=V-f!9YFi x Y*Z9YMKQ[1^ٕՃD %Snͯ RO-rrf)M޷@W rv_yDS%7#!А`DZ7p/68BF7K)Qb~](̏|sg * KupD@)߭oF&)Pws?%NXB^rS5y|;=_pl+cӕ˯Op|bn:)gê ߑM;G+ s9|,l@7ƢlA9}eJ(ݿNAmk|; N?lhk4ػ1TųL)r'pa *3!3vJ>4EAB0`< eQ*'=yW&ńZhU7m?{׼MK+wތ p:ULVߏ/2@c# '^X;z5xpb7i3G [fDFX#EV}rNEs!iO2B!C6/1PA-XTC>Ԧ#Z3LE֌.ݤ[qܫ0^f0y{(HY>{|҂X픮 8+$I2T;[0B-篁l_/2ǿp6. @Cm) %>qxMJtȳuR nux'MԠVD>5yOw*wB˽#R)W2BWj5[cGm\ 0jH)bk! Fp2- vt&խT2;ryΨ 7pyTQtSV.]*y׈;UuIFpx(XG+-<5#a5-xD,4BfWLھ"e尼I=2 hu!ݔQ(-ٺ׳MCgɀC (ϼxXu,Y(?AnFo 9y@XP =YwLE@BRv|؜?O=~ګmz]F Tc#c w0 wmውT 5ZZm]sT&$gdj5D׎5DEGzg{98Rv7udU. b́EWĖx!HfωWzVTm4ݼ oa]oNɶiS"!?̶hZcGT@7Dg/AA+\My`J ɋ ]Z@C> q|pGYC*@x$2="b bsXvz TtgJHW-e;a)CcD~"gd9@9lulQZC?w-rK<.)A3 ų4F߽Ee6f~3p%d8wb+2>u7Y:ڙ}1KM2Vg)C B N7ms7l Q~vl9r \;5=' ?33x%y{nų =, FAZ|*p[:jܱ9E~,9 xlLO@ p_Fx_eWYT -pbVذ዗/;[M. M~ЁO"ƀ؛WK],x7Ҿ%w1y׽e994v*ă"o nY RD&&mPRYt׎yh w_o^* ?Dv 8y9HT";T'떻mU}lxdp*ù|43D,B%($<xWGpl^YةQ<\9-HABr(&Cv(jM4Ąi|6ƹxG2O0IHأOc i\$msnp|:ꀖH=+~7B$ũO| 6 R@0C*"@O ;H3Nb$g[;AQW1S(&{fZަ4d58rW5I,޿JnscG76Z H$,G7>/vQ]swkg0-؅kaYã-v?#g'+VtO}Թv1I$F>dfǽax k(k~SDJps,/ѓV >>-5ms4o3a<T(O<'ii#5pgճmg 9X{E{TL7ےשTЀ6@lAVy|clWcNJ'F!ؾ\a-bgBDNS}SEv#x:v;xKL.Gj>_j7#j5g VF>;CzBRӒQZF@c?l{U ȟZQAzh ,3 |k|@L=-@%ӤXe;h, savP̰Qvq {uq G`<Z6MT"8ajAmK/c O\/su/y>#@E @ 2}_z*ŕH໷Ƒ ۿbzv< PY-Z8fgK,B4v?ڹO] tӑΕ$c'v P!w:@*MTIv|UkWQl##}c侹yy*BP{wvG+ 0Xjkmo=9ol sBc(O 喽p=s8j^-cmX7e\|߉=LqmfM4/Zbi{a' l*ZmDebNa~RbsO+OTG}U--/e1/(A0"VWj?kI#3 PC#'܁(Ǖt$iWCqI:kb8E]cJh>g=<[B}ybz5G9.o3  5;fKFΖhlE(H/oytF^"w1%&[@uPbGBsZV]aAo=~`R1!gQoZJq(.W@@͋5L ^8b1at7o1q@Z*;zȲhoЭh) -:zѓ)H$C.ߑ8Z׸]Ki=>T!v;4dD2t޾31ƨUEzKb <=n]RuI5::&zqĩ/wîrkisp)~D^n >2՚B.K6$yPWq\z1*SV`H4*4xl9кNJ4]s)+x uW)!9SQɫXUHj+epwk ̟f yܮ )wԱwП{6.bޢWGX#Y_2\4Rlb_{|j2?kp_|nɴ̨ @&xIA6 w&q _s cwk3T:]ʂ%f[3O7Kف7M~HloUuƜ[mmyQY@*`{@ٹ)9:xAB?~'-*eLo@&,Z/P 0=`Y 'S|5D3nq.4@'_`ÓV+VIiZ3+0/OO@"kij5 LKC4Ji.>G1/y'5{" жmGqIkE hPkߧ}$V/T̒6nl4T5Lj!]:[Lp;^@B/GE>c ruV@9"0m 6\{0k{@Sh%,^ M3.Ǯ͟8O`M}@h2gXj$,@a@̏WYk~Ws>A"}j*{F]l4 .G  SB [uV㔣V:@;?3\ 9@1 WC]`.z em]u0!Н}51ֈ 40";,z,w‚ %{ )GgQfi~J\3A=eD QR8y1\ϳ< 7nreBMK'|Xw!:A?z`,9eNmpˠxhr=[(ߝGOEpC {U$«|Ms#*䠴HѐZfn%{Ϲ: MMW2}tq"Q`k >kGCW>YpjcO*yǕ]i٩?;^3f6 c}~Ss~(2Dnxa69x%EK-VB\,=#P۰b7!p#Zr!@Kyd]I_=ʟ>EJ5ʔVƗw鴲 ] 3gJE}%tI^wancw ?@t)ЮKabϐڜk]Fi.Ҹ;FQ'qQ`ۗ[׼=`RzC5a۹|Dy#o@,ҿq) -7k0u'Eː޹&:poC/NMf6?֙(9WUqxGw5hÎ_wU#ԑYB[2;ܝuGpKmz`7oAƉs,S-R>,wVwJniكmJxdQ15HN5S&eMs}Vǭ l)Ft5ŵ{H̢@ GzgfoMs%=.F3rr >^ofܥi^ x +N##h_2V:@3DגnK(_cSE=*<4CǙ3㱶33jصM PI16)%}({TEwrkjEw ֋)]5f-P8;g 7'"W\.WE;%5a(u8Ld8n *a@_9v-9UeO$(=*D/Zc0N1M `rif9ӹDfrfGcO23p箜KnH֛wK&}S;(䌇wP@Qtl?霁ō cOv%4/ VU0dc_qVA`LZ̜ˆLI1w{s>!遘?#vYHQE;f$2bi7'v=qJx&g'$ԋ/NViAC3Ͷeŏɨ55Va hF #guV>I_e\/{ԌR&thoLK3<ˉEVZK\&y987.ͧHf9XVtt8+D5ss7 ^ !:Ƌ&n' δ0-]x7FS|/+tfTCnvf>"9;+*}[yB.usui"/ǼvP*qRfFN4fe"mՏoĻcT0O@U;[aЃ|WhvAĉ\+TP.2C _lLA=3sJB&r<50\jZ26|c1BxxvEy-.'YPLq7^50t]<[NQs @SDn|iOqoD p0IQ]-vpFp9B>l]S6X'6E J5-¦SF_Ů)a+-)zlFЗf>f8 )y`"ֲe4vq HFX5ȶ:-J>p@|֝v]r>9"V:س¥JwܴΟKH2%C@/2/pg Io =7jDrs%yoOc.ښv"0@~GKej=4 (syy WC9fc:uUZgc4FEEg"/ЖS X1Y6' pP.Qks[1#6Mt11lH]E])OqWS]\jbJ h˕Ħ PuUbeGspMBM'?SM˪.,/-5sy3tpq8寛} ܔmE MA Nס@+J&74eXVq{(~،8Zx*bW8 VWY"VU ` SNzT&~}d؈90I1_ystOBcmN{ Ov[X/F0zgUJ,ӗz_9`V]dg~EXCwDd_1e Ӝo{*86/!لAC<3at OIln~  ^<{A~GXAWk&Y?ackt U"kz+_Y3= zZ6rD2}75EoW8*K|^}򇵆 j `:beJb+ ji՝-, Qh[HgӳN8Fd}}a!e"FG(5ehNP0Yfɯi\p(1e Y_yOl)7aH/ C܇ tfh:ӽ M´=ۊ&`H%3N5q:S`8]7IU>w9L{&|[+mtRp76/AGS9xPH=58`$@ (;zʊr9G /Iy|~1&B,>J"L}-DrW.bA7HHɎ2 q;+E&*2]3Tʚ:>|̓'?~4;ƺ7="=bX6_#˗dön0i/ G֫ +&CO ^mP_BP} jjr{%$$g#sɡ1 5\s!齃'Z͓z[=];ʩAVB7)i՞poW: DÄ!5F`VT8E bmv')Io,J[A6:'jhض' J_`Bnu]kP ^FPGUYt&;5fV3XmhI0fuu3;-~5E:tJK+ٰr`2>|j%sн # ,_o}.LuHI&tQ ]߅H+ᇦI-)>%:B#2C7:/lNBL5)s5RvX .u%r/6w!}"Z]Y@ÒcDq;xo :*X7}Ui?O4|NRsjLv[d5Tn0"*Cʝ{t: OF#I{gC`x1[z*AhI@&; ybݎuuf{/D3񕄠dj7ZixymDto\p֊eu&̆PuwWc삎]`(m˞^ֻ `6pT Ύ{`*?bkKK൚QN1!r$viͨ{?+nz.9MR`V\q=`B7Lc79bIHckA"`ز4bc|ry( WQ{~짻`<9\ fq-Vj"p{ZL?P;p hQY!raH~\W)ZUID;~: ADVH61zUBfQk{4 ^9US(cnB!!Whls*EǕϲQ/'014?hLlwVZ ${[J~NcxT ƿS3" wӞA] ÞqV`Fԫ=["vs~J}O*;iJ!ӏ X@{-7HFr2,,A"l&g(]4n ^'S$ѵЙD5*(wQ *Qߝ\c1%^覝;_z \98Ĕ1\ f0O9ClkkN<rgEm "OX i.MR;x5|YOhwg m-#1Ҧ@+1!xx5K 4MV}5O=B afM!~Ν u㣮qyb$kJ\%cv]_gD9BvΛk?P(KmۼtY `:WC IU2@rign-`m.ŗECJEQF!,P7C+[;mY-֔RN_xM*(AbghZ^%@MÎ'*]%-u)TAԥ"˗u9Սv3>#Iw'J7w2h}Hs$Ȥ&@󸗷TV7:F5{3*V#`FyΚ:hM運f~~ vQzdEm!ф\8hvG+K@|;)9Y9tQexNXl&|ntuJ+޴/,&!9z69}Suu_brix[򘛴*^n6e7^#Y