drbd-9.0.29~0+git.9a7bc817-3.3.1 >  A a'Mp9|jnԠ4sWV(9}G=j8uךB0 ބ~%UH5Jq GB#zQzLh^PZ#C s0{#[IU?WIVZ#{}$3ŝn j~qVG5\(n^*H홧(GUFӁzY(V M; AZ*ۿՆ?CePS=b7c27d0126c9977a39251d793c848ed6984cfb40645d5918b1b3f89e6e85b131d7f5f881d054858cf8f60408289f035e426bf7ffۄa'Mp9|E_Fל(=ITK$K!AZn).6TUu?oBW!Ū-u1brl>) W*f,˰+ ZKJ Kaܥ` x17{8݌G I5rMcq'\T>1,f2>.ooʺ -#Is)JM0TBEX-/<[G@Sؠj[ D\4Ke"Yr"BfwnfzX|X>p??d # ^ $04Mn      0H(8;9;:n;BGHIXYZ [$\<]P^sbcd eflu(v<TXclpvCdrbd9.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'Ns390zp37SUSE Linux Enterprise 15SUSE LLC GPL-2.0-or-laterhttps://www.suse.com/Unspecifiedhttps://drbd.linbit.com/linuxs390xFFA큤A큤a'M8a'M8`Ja'M8`J9f66086a7eaa4be35f8fb8e9a0b1fe1d7420e27bdf8863706b205596275d22fc1ca3e8f71b7de618968e7ea9fe47822d9e704dc476aef8544033abedec355225servicerootrootrootrootrootrootrootrootrootrootdrbd-9.0.29~0+git.9a7bc817-3.3.1.src.rpmdrbddrbd(s390-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_Updatecpioxz5s390x-suse-linuxdirectoryASCII textdrbd-utils9.2.0 utf-8623c84553d7d647140c6c0548bfc3667f7af237758c8c070e33c207b5004a851?7zXZ !t/WJ]] cr$x#Ez/}hlMw Փ2g:i5IH>,@Q5H5R^(eEjkHCՄcJݼdߍKcܜfo9dD+Nf?-]h 0Z8d5/E/‚cޢ.l]c&J1:a\?P&ZXw5BC̀f9Q 5\?h37ωZxŕDuEF\2$54 JY]۠K8h,$":1bX5>I!'}1)ƘXmP>b!N{4m򻞩6bP\JX b3-(ZD^ۉ bU`F|3f2 dˑiÍf Ž풬z`Ūznl4.ΑsGqVPĞb\N->HоB1GxDCxX vӵ;sI͉*=.S*hб}2I]9TK\ڴL'3pK4]A]y?Bĸ0THp% RI8v':1Z"xs=wJ@w݉ {3!{U :-Rë=g KۥF,qn} zp]QM P x\NF]R[7j ɝh7RVWx b'gl!/7VMFƓDKq:CIw bĖb8٤$~ͻXƚ% k]2mLR,U~'u [ qXǯRHf3h8Mٚuq~tqHWIǏ/nq&B%EӻOF͢0eޒ"KB!Ln4AOrPkMgv<33 v^DIq7^(G[ٺz4W_H>﮾s_[eKh!FѪ&wh r vxP,&B`ߓ'r cv]V4 9Q@jkK_n`ETʗ0σm9,#O=b\ۜOx-4 :u0WE.U#2BmyCߍC]+Y՜w_mfF^":SAlQ E'yA>Bq{`˫`Y8vAHrODĩ׫:5BP!t{!~(&rT["2Bۡ\_05Uy|0w/e4VMr`H"&$v( ubh1)/yz Z>տϞ)[CjuxZ-DOWL-r.ΑK2_U;^B$ \{$w@I$POwP Ϳ gN*r_5sCB'E;g Hav{g.ڦ4 a:chH W W\g G)WM9ທs2W~U: d f_dnR:ҁ&L.a/ _SW+|,"|n"n%`xwA5.1d"9ՠ/qP坤۷m4YtB@Ɂdkx@9\O5|u9`:9' S_>"2s6UKxe4N Ι;>镖|#yxCy%\ ޘ5n8Έ~b^/ r|{.:*UjTB=0b;4ݥs7 hFmNCL q3buU}Lwc!3ӕ@آD,?TyYCbN=Gyۺh-\(n-nWpհJoΖ!î‹tѣ-x (w]fj5A>c(IMde4V_|Ycw68բ[ߏ#n juVt݀)y{ Q;oV|=ZI}Wޟ-&).S#~.}`oRBW),@5ẙuW| uUm_mJqʱi;)O'0?M+C*$Lj0EjKĞH(&)ET1{OcrtyNPF}ɪQ,PƦȈutSFZ&6Rh"qOt_0yɛI9d}Oc⯈R Oѵȭmb$03!^(3}Fp?Tې)3ޡA!}S5?1K[b 4Xc A [Iy.g孨LXIrX#2- mn~>^<ķ3<];"2u sJ:3nEf7uI2*_ oK@H.VhXUˇãC@s#.a{7%_:b֧zG즳\Zx"/R$4ص;1џ\Lq^so<DwFBBEfrt)v3P:i]!,$-3xGKc'N]o(@O8SXp;M{mSXw=F˗7 ZSQG)x 5ZBIKe<}+ߣ~|mk 0^u$gbqz/< f2ё -y0Q&ρM4)Eo2hO|}Cs.mfWa +?zvC.a dY) ݏp&h4M:,B,HȭYy3DMZ /cm5#+OMB%E*L^8*jaf^j0J?? ҥDw*$s3ƼK@DE4!KĺA'OPvr6{U?b{.(da&2fo=p9uY\"7;; x a FO+?N;V%=[-pLnʭ %@!WZ. V̔Ph")t,2 0|Y{EeSةok$Ezw,QEza7~1p-/$x^*lkr~(M`w4CW_VO5Ȯ1yLL%6I=,seQ!G* >%@) G-O79V,ycPOMf1n+f:{k{}XzKey_* (xX_ B F:WUH~ٰA q Fٶqx1]A=Ġ)*%ͺ1/eoG@ t&:} 0ݱmñ6$9iZSAsI==*ݠRESۨQĚa1gtb{ }єeMY*?hM{մǏ),؇tXTxLC>(S1u͵iGIʔP҉9} ЍwП{ď>v0=Z6D=$JϋS˗U]ؾ#?x0&2HЇ^A0j+?c2 T ɹR>k$~$ݸ4O5I'bZZa1'AW-FީL a0ϜjPEka~bwH`Iй:'7q' ݓ6vǼzτZ#Z*ww: s,%4vaNo5Aۋ<;EiwH wT 6oMZ&s Lc6HA}hм!MJцh X9eLRG_i!0{LN*e=Y K{Ze㝭3" |g9rxw)M I'iʓrF!ab;#Q[}Y|.7̔ YGgM^e!Ґ%nt_Ѯ?]ؠߣϜ[ -̷tVLGEw|L ^`AI'>[㑍us[X Qb'aя1niUvKJeZЩǰ^["e &%3ӠmN9hG_>M6HAՀJZO⛍1rf4hnPKx :o\҈ }tahKi {{u-,r'%#u4JfK#+:7gQE*kz-f[2(U|x\I_S))7iVßW<ö "=(Q/# ŏ#>DBOAm`>jx~6٨:A2R?p2Ar*F^Tq#8˧Q4+:r>|5:y:Eeƿ"C[ŴY2;mnh<r7/xH^b;*#HtMosrOPXi8-ՒpWȯRbp2:<7&X:*&7T.*Rj|vkǪ y@G rë܇_X>_p"Ë"j-E6GfC[_ZPS8^L,A$9|[ ,V2G΢pN&گqY>﫽lyppLM.{%1#sJ*d9E.iX{>4kɝӪ2)@4lXOO> 1eV[`Bcua ?.ա 72U=XČߤ6H:n3]u~H.e%X[(@BH&;_R _cޱ u>rPI"$QH bae&V"6$Kp+xꡜ#z_Rʎi;wą^p ]PtiT xD18jAp~ۻ߼=nhEYHd]'enVj6~8`Ķ|f!fC0گVb~2ypVyq]D`bag.aq'0t-݈ovdUG4 =iO]|C`Mz3`Uu啧($̊[C(;a{{W ժ5*µV)`"ޛK[#aTD&dۦn,[dX~Q~|܂d/[SIgn}g:0hiuz]NJ6:m|Z(ʶPׄRsP@/st/@R :{+ udϋpA Q??2= :.6D`& ]h` pg,3np9Ҭ.߅ =nFmafd(w,d&QA< 2$sR)iPN->G ;<[,trtlz6D],v yE`bMsttuQp8Ť i\p̨%b\ G0HYkkf1[=+L00džoзGE*GkYa|YBPK R]/AjZŔW*q}Ѿm)t$! ;[7},-R h&9g IoaL;/XU)띎ZJo۰@s-ZN;&KF郪\\O{s5V>#}-,qFڡdPxx47jl1F/E(S"‹*x]WE_1,bK?:8ak;ݎ|-^_ QYq;<ۣ } "*).ֶmXs}#{h(8+ @w*jG@t.'@ nS3bo]ؙ%N@\aϗI- \Pc;5˯K Wl ð5O`uWHĂd38$ՀijJ߂MJ Y},Oh?lg1f+svUmčD[wq1fv8Q)k,{k/RB2bS2ۑ՘kr'.lT~CMNNPt{+m#: T(־pJ=ظȔO5 6+^g( ⿺Iy+/ 1hp ­&9m˱ [+b*0{ ';8V!?P-FX|WWC.5zw`#'?8 zb@ g:WZd6~ui_I{w[(R X2Yz/1b."V>1w,q J L=?zO}Yen51H{wz:*؍K";"j]&rM/?˝[diCL֨Yٗp>z=٥Cm"aŸOH2}*M+-b ե!;$!q A9&OK&N_cL84YI'*QN+yKz5]j=.{Z8}eUpn*2 $G,/;z/e U;f|g &+zדBK0X1U0J:Ya2nL F _'`}0q6mө+2h_3/>,;@| Px70P5@{Dx݌wgLlEXħBCZ1w 1Ŧloв39)&P"xÈ,H"AD$v~RŃ33[ yivvfA59sk@Z(:vdj&@Z"@aqhHUkj Nh\QerNɱIEp~L"9 ZRlUegwcB?%mwglI2Xwq߅1+ (uk5"usi>S{>v` Ȣ<7MѷBaasfB:16Kޮ'ή GŦ 5T\̐MʄpʺwZ?EvQC?m,hɍyETWۻuV5sWfa%CclYw@[ƽDއnaY?!Z&Vͫu3|'#nLhZthfzo=tT H#|u[skVArME܃#+EC,&g,HQ8w-7q4Ҩ,}[\s7IzV3%_i_4wxl!chz~[ qbږ&qC[7mv\6=c"5W dƋwܴF0什Hi ,cs\ ~iƓNg;O;Yldl<žŰm267y3;Dk}sGd/ֈ(N$S75`5dUf@h5\:Wqy2\OzakfCr/^ytI !_kO*G1wGͣXܟCvSKhPNt-OѓͯN0P#Ozml '{pCuZu0l`_smNѿFc~EcyI;Pv䁒n*! k_$^-fbØ2hfh vV zN"rn˰q^oA1|<2}I(Wrgl4&$RB}^~"dKC}MЀe=lNU-fC<-`=/; ࡯O %ыWJR|b@a3 Ȑ9vH{QWl-7}2>aK@wc;HZ}!z֣ 0&bːp]/@FŽO#Nʩ`]XAk<\ӳ7 +dI6}-}{9"׶` wmڌm1B0CQcDC;Wwr%'l2ͻUrS.*38V=uT^iv`%2,P(Cݰ}g1kreBl_DžqARDDh=e^Z&,J6'*ʊ1`IlZP9LDT FVYҧW/灰1,RwQGݳF.78kutGU5 ӬH=0(I@iKwo,=[[W 'M_m}9Kc o6) ;ͮ+,5$p_3l;vKБ2@Rz1#&1v? }K8 lO6Elvw 7́vORPt fI~an.bD[q<gU5mvw(GPTΑ_N"FOykVOFѠ1<]axDGw]9?  !}+itqytpxb.guEǘs& PGh h37:#Ѵm Q+{<xWynZK` QRۻq[nj"/ÕZǍȜ#A$7e2h&%x1zK&IyhdB?T(T [dҬzD$jcTo]7ERoxfI8-Xv-SGѱb T&DVjt%uY򳾕iZ15g48MgBg vҁ~1wdzWU-jBO 4uZAe&ol BM|)m1Y Kr@5viM)#(zK!d` ȸG3/^*;Es9k Nx6_Fn5"qס)ZBCVE+(|K%WtLcž~ Z羻\h(p+@^jLX^ND|?dsbX3E;ْwnJdM^aBw^t=#mjm`)lv=bק+Ge<?ѳzg[QR* {*mkxdl!7ٷ&O&r{yM= 0ۆf(hc,2J*u29232 Ru -[s֥{bΜw.Y>}MB UJ@FPf {fv7D-ńpfqX1#tRlS>/#OFo㣧-MR"T+MV{>g^6Uagc7J6zyXaBlNx}pHWf4oAӸU.O\Fƃ{QE V xZS½id{oBXeu#p䏠xiY^d23ytunxX{dĥcـcv@nY{^xxq's"u]38d?u)h4Ķ{:/|*_O㐀$[+n$pӢ S=Һ*ޣog&Ou&IQHpS j,,ַGlbqdŠ8תzk3v ufZ^z'yiZ[['b{߉; u߻;;$YTwfxxE^Vszmޮ0j,0~OB0ݩ8+^1(/@mWܶ}8Ozh_ߊaP/P9כ,>Z heګϔ4.yzSK !. ?JҢϮH5 B2cGt|C<X99Dt)}f*U[3k`v>- Dwn;ZH]YycӅ 5y乳$ܴԇ/pToB—"; Ǹß?#V=AFJ y@T؍ ©>+PO?f̫z_g!NuX.dV')`b@c@**@60H IG*IYGmqB(X+) -vs )WҾ1d bdRc#]`v6HՄfW_02b$VgS擬޺_ q4VLC,W'ґ=HAlR{<݉t[0[tʹ܄7;ZELEϊ_ĭ<'jRgb.kɌ$#f ÈaK9"z,]__n5Rl?"eP&X_UZ(ߚDEGd;zם.  l{ǰA_}}~^ /ceA. FCfD3X#_MdtotCzlٵ(q%_¡ힽFύKy\Y ,|ӵ]6Ah]Y)rIa6֨2\ېcv2gIG#W_cػנ_O2{v xg5\kr@4@Jz`mv' a i4W忞g uhoΥRVړ$&R]AxwcҏVȬa5\QaO;v eF\BT<ʒgnm =F $bw2+P tҖdGuOvg˾ēD[iB$ K7wCq)oP"@+p4ȹα]fo>h+k" %|aaO㫆2CNұ4( 6lֻ=C@t똑0d+s)~c)`8dreBHJx]BG2rT}mxk|ETV+nߓaK2w\ A^0<[fiiIz z j_u 9h\*8RTw[7ЩIL]`@I@U<` [Bُ2L܃ t C y5\X;:ab.„5D]acԎY>B[a N+H I*ዙS ¶Z!E0Vp#)1d^:|hyZ-܂n+/rrʹ!0zXҴi!Ͷպ(a%ʔݕ%F9, ԽO|zMH .Jsvb󱗇DY;AKnvO`V-  Q) \/ca52fޏN7oӗ[S˗.IS?o6 ?啇]֭:ևg\ϧWIt{V< $g)qMKZ> a.% [#i`o՚bkwl 6ZQRQ[>9boaMݿ/NwemY^ [<Չɟ4J靚T{^e+,5٠Q}NEzB :mZFK23o=S"j[}GQ-XH8vny0;=&!t<ڌ`$ H>bײ% Z` +XkanYgAQ"z :tN6Z0?R]c>)`Wp5gŗi`QGzTq8xH@YGvMŌw~;՚_bdۃS)1¨Q-%ʛ^ܪZd'gۂ$ɝ²vl -S9٦k3Eۛ+-=:EhR7CMenT(PKXe6d9="@^Z[?#Q}#e&h$5[$ƿ{p(>[ ig:<3$WX]BFm8֠-8QI6r;Xb 6G<ɆUo*D KO%Tojʯs)ؾ:hԶ YZ