drbd-9.0.26~0+git.9114a038-1.36 >  A `!p9|!"ʅB8c_ezq{FPYMNH&϶b/Pr}j2V&|ҍ$*Ry\`|Px.>krLH;9RhѾyq ߄r7y-'o o~˳Ղ|Z|r=.%_&Oj1j?gb'?&DIB28CDo'k)6>?éȓʸ!'s0f57e993076f45d1ed445349a1b3ca9909470a7443aa22a6c9329175d52297c859bfe95a76d800355e1d814a13739fd1a0cc8f73`!p9|vu5˘TzMJNꥲsJ;7!6 >26FKp|=-NLw i f񒇒1MVOVGgg3*۬5HB8 .^ImB^jU#{L+qiqNq0 q:*pqhZ=n39tŽÁiPulnD#>ms4R yM?7ci!·&KxªxE72-hq>p?y@?y0d " ] ,0Ij{      ,D(8:9::W:Bv@GvLHv`IvtXv|YvZv[v\v]v^wbwcx)dxexfxlxuxvxxxxxxxy,Cdrbd9.0.26~0+git.9114a0381.36Linux 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.`nebbioloʪSUSE Linux Enterprise 15SUSE LLC GPL-2.0-or-laterhttps://www.suse.com/Unspecifiedhttps://drbd.linbit.com/linuxppc64ledFFA큤A큤``_P`_P85179e916f6a70f49ea43c716306dfc044d38b08c8b8f46b126faeecfdf39e4e1ca3e8f71b7de618968e7ea9fe47822d9e704dc476aef8544033abedec355225servicerootrootrootrootrootrootrootrootrootrootdrbd-9.0.26~0+git.9114a038-1.36.src.rpmdrbddrbd(ppc-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.1_м@_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.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#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.26~0+git.9114a038-1.369.0.26~0+git.9114a038-1.369.0.26~0+git.9114a038rcdrbddrbdChangeLogdrbdCOPYING/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:SLE-15-SP3:GA/standard/cad11caf11fd8839b5e309607ff1af12-drbdcpioxz5ppc64le-suse-linuxdirectoryASCII textdrbd-utils9.2.0 utf-834d3e21a853130c79ea3b49a5f5ebf1612a7829e9b6a709a2e45474f932951a1?7zXZ !t/EQ] cr$x#Dhs/o ,, zD.]mafeFi'\wF/htoy[ψsg?K;A4,&tzwxfO0eVލ55[a֚k+5IўTF\,;ɧ4[$=XfE?wD6~21hzdmHfs-syCB,[u, z!yL|QWȦNS1-̄ryV+e!G/;T !+4Bu%Z  / W^'} WuHդ1Xh1.x|Ӗc#2dk K$NrC2>O(Hqюi5Ln7y[ѷH*tNNcӼ?we?ff̕w]lF4N߅!<[ q=7a:WQϯQ/4ܺ,&Gơ˱f]'x-Z0 Rµ&5Cnpnn 5VFb)ܽS5O%- ]lOm3݌c8Y[3eLrlĸ ..@(}ZxM RceqYQ6sMt5N0\=b%y8]C4|gku ^=GVĵ/sp+xIۡB.g_Z(4Vu B%ã[XE~|!qDy9mv$Q|0n9@YHqX!-gw~c} I#c?ѣv1R5f苡!VpfʂnCS&&9SpiJOQ^\zT4_K檒g-(Ehr=|:\xun$oZ;O,Fos半=.4РT\ gL`K/&"5`hWW WW6a-)9乪 7PgD ڮW/Y޿H/=|@n qH٫&jJJ ߥ,Jm?@q]޾ȳZ7/2k_`KJhG >Gk&7klkƇj@ŵ-gzdOuZ17d}ۋ&Ӷ/懜Oy1ݣ?>X</}=`+|о :χy/^$% kcjZ i)ߦcGئ4#é":~X90ʂ 3dW 6aeR"&Ӥ- iPQԉZ[O66X+ u[/0l!pĽb\ Dg%|>SC;$PdbX>]B3*~knNi^x\ig~s YQ"7l QFԻ'AK4k(v"L]=.jQ*eg>* U#"mȝg9Ye1cņeyodm$*]z+&%^ w'}>vW_`:z!҂rX3d!OsqGL6(>8m|Ix:^3Yu+hEgwUl0?R?}g)J9z˷JྂdKL8->6 -|n}ДV3:{c)2w1"G+ Am@ۯH };ׇOQ ቟SǂѤ%f@X8\ briptE"V?ם);-Ex@<g_|f0p< z΋ mڇ[y~ ukR3]g""!ihpy ubȵS_;F^Ey 0$Eׁ&d~흱Rq+p ßH) Yb"WnJ|QJczZyͧ*9R5;Z6&~~-CdKJ4=y?-[[P$&LD%"s]+n<񔵬G$ӡ[z!R48|q+}q/KøV_5pī1?JU.@r.i<~ذK >NhK 8lX0INZΫܗZԹ\ZCrv6д e ϑxN"YIƛC(; `ߛ/Z l, {5, rJ)qCL%Nf2dq(bg2\[FG^KlMsuElVh8-҅~+;HN!Ơ"#\/E8G&QW2 /`q||wz4OvuJ- -φQ8ma@Qc{#oMZ~ȵj:\c dέ!a>H]~&5c?TZ-aꌦ=`:N_?e,;oX pL>`)؞=C沼P'9ꮡ%a,9`5M|mNdŻk -a S=tl,T?E6޺ɗL2!z>cjtvu(< Qd׼LN s̎|n  uF/8i;Ӆs팝yU:p/a_j8g oWݤL; -^Ӟu)o8ul'I8Ix|>P-:xlf٩;P 881^;ơJKuVVC͘AS^ YӴINht+_$2a;VyF+;|Kni?+F>̡/B)n 5QV7pJqlVD1y=c95U,UÜ}rM7ȠAݴBL+Q>E? ga Fkf} @i\*%L&ȃkr#Sn¦RW#PΡOF`'->.'w H%6[71l8e]κy|W+^h*{+셈i#S\ [Cw4=PS4G:K+Qi(;? J7eàflZEYZOZ`2H}l%K˜6,n{Uqo;;fhG+JuKPR Y?H0~\ˇiXZҀD&+( M‹zbKVƆd|1T,kOVOlFsXd7o qtwh<^IZ 'cY^ [tiLg*pUb5*DK`.Q:9|ޞ/eڰɔ\߰GG 71/!$8Aĸm-S)WW~&$]Jͯhc(>; |E/,jwcHm莧wf)#8]>Gj*E :c!sYкxJGjMŒK/܌ˈQ1[&3 E{8mPo#SF MxN$>[6 !D웮[m2 -:Zu "uKV١A~90*G` Y]QmŪ>^8$zyq#Vy]ݚ֟s/Zn{e]oM7ZYF=xZ\0ID:CܰL,lϊe+8Xj8E38E(b[9Mh]U 0VxrOSc=%¤kX̜b~S~o JB?=}qI4 7}Cͯ`XY ;C-M$Y7َbf3XgAGk!`|mGK~ƗY:(Vc|{z'_֚1m?rOU|Vy+ .I8)+; !8$-m%vGYuku#z^ Ɨ55pف}D?4yW3!j,H.?':%D>y7ာʿ̫/J^j@õa!EAl-RU }zC#Wm @?Sժazy/RO2ӭp.;qCs5uJ0Z;~aJf M@/u-x$78@hCBÚQw::55ًXӓuD.PQvYr'|Rq_H2Eui⃐s8 л,D)=|;~ͨ06N,Wpj XthT*Te3*ǐ.V ΍m0-`ϻ76p:ZlKF50qKQAI_rPoJW_wu?1kَ;:;E[j6.@uj7+hո{1羅'*PGed>k0JvD "0.d;i`~-7j 7U9vYDos 3w7ħ6k]IYifrLNj! F+e,gOh\#8|zpJY+{]ÒB|6Iߺ` P_t]!1krl@Xsc5͊-K/',J+5PeVȚDo"\yp: !s^.(4J& L8bƿ(Q)@-=ίR\oɝ:IsJқ% &h@FmdC2TndneSXidi@]zD?4yأsZWA!Cܗa `Qx"i]}2Lh _7"S1%=G0> ! +E(K!ck)?x\pÛ f+{e 2uwGbo<^i1s1R<K9ET#xйjVEܘ7~sN~j}] OWBLٙ dR8SǍr^Tg~"?SMGSs!Ra! sHCL&\#FQq)Oޛ5EM%VKLO+oҍs$u*U.1e[Kwrl(q7sM6y R%#ܽWe= TcG`DCu3U5L0=4cr4$;8f9؄e1v/Z)a,k|$Q3@m(9$3-r:}yby(.}A:8fM_L|Sp{v&@Z(jۿ)m }7^̽j'lRq [fOBIWsRE zn܏ %]k$AYhL|+u|(9]Zla#WN\2|3{6$3q}TmdT7i@+Jv>^f458aj޸ތUOM!Ty=-KLwB߰8R_"z.1xxlw1@l5?pAI'­sa>(v?;K7x~P8|D!tE-6/yc=\;F zɭwoslރd8SBTy࿉.-$H'fǺ\ތ_N)y/0[hխv//D#I,'x KRF³/Wo k8fwء8i[feD7k2a10)t8\FIw Ziy뻰Пށ&Y@af43k@>' nY3A%RnR"`zB>O u'oN4urlQt=,I'&Zha݄RX;ÔG(q8.]vP\UOU Rҽ`wb2 anpɿ4< pꠌ9+>Ҭ)7 Ftm5 % P|N b2XAm3HA\6$0L|H_M)nIZ)r$р}8ms7n'6L΂փ೫ /ש5 4~\ rG(iXHt0vqH tC. *E|- mVph[zuc4t#T[=0(d0 M3+=ܾ&GMF@a".Kkg唌_>4X"^q/bᗣ f!Ky|DA/Z=VZ&"k"I]']z/(ĀIAlB5"O T znU@BB`v;()kc:Ǭ"M2 qDnx\kNGĘYD:G3E'C6_oȹ@eF˕"ҚA\^m-@Z+ Qtg4 ȅsb5L>߶̈́NÍl.XC2vHj]ij۰BiU7GԔ$ eh]7~:Nч0 C(9ʣ՝[!yd^&A`NZ@Q`LWEYP`)!n-P*Rhѯ'Zj~tv +N-puǵf}U-tu<- jRWu*_~}ħ2W6NUW^ s}6-=z$L w%+VqRiLaAm+A/&?UmbFy%ۀn$d#=WDk(F=U\F#}ʗ4A1HH ВPw/,S"ףDCZpr%Ir:lHuMl%!L9"'XަIM\lh.q.\ЭѦ˃腧%y/6ﮨ,DD~Fъorb::]I1Uw8S$m̕R{ s geTzޢHa:'؈@5F@)ܱj\o y;v爓 54䋅t݉M(mQ.N_Tj%p`|(&nwW/PW̃^tψj~? mZ6UݟԞRkѿek1h_m Q Y@ѣ~h6 09?-j\rT O yl&xlh#ђ&>yuaaҕK `% ^=3g~ JU- njVTWUBL~"n|JP0NVs~: }]E"pLIp0XYOD> 6qt@CS[Pǿ:/bPtV3sA-je1ӂGe,(d̶>vxCmNx4/$b`m@%Pn7a|߀l'@ch\DQX$%L@( olئrh~i^_SU[Ww&(^ӧ*mz@RQߣaƒ—е@ ?y7w=V/`Ъ9o{uc :eN2Ov(XG6j6X)=')G"*G䢝yC2vz\,bEZAqm=H9;vccMt-8YKMr`. ǀ%;)P3vqfy!ew׃h+"jR0 㝝7 -hj^_*B71?h5e h',ڂ4*O  $pve>;ft ќI9 v-⚟U6e`vMvR J@b#HhϹ9P~hrJfl^57Hv"X1!MjUg(./7gVGcˁd<@}Ӗ8<3Acv,:bUI nq>y g!"՚J ד@:DYUFdKSV;׵HR C;Yι6K8AO %6~g8V;$M~k*m_sܐ`XVg42RGm~#V}CM7o&F,?4itSnPe+Fྡj운{%eh.r4ֶ)r4Eۚ2uG_݊aΧG|mAߤ[i6𳐙fD sAhs[)څ#7Xnԕe7_P1>9[Ft= tLU> '%C/XA-ܔU$چй> Js0]]NF̠ϗSFJfcsQrk]҈6Mvs|Pta [;P2G}GLHf6LĊDZdGbSaTAlxӘ{{J [D6 w%1"YECxH9?LQ''q%qӚ g~-ؼ{_TxsZĚ_uOv1䄃)C@I2TX fF( ڨqvk4}, ˮ1~ z?N߮}FP4zlan+CO3dH>A?:Jx/Bj^t =Men{ESm $ʗP}p?¾*ϸ2<]/IFx:vSj*cD 6[gy]&:[Wa&TqzV=A0W1$sIzT$FIB#(IKeTʝ@|g]aAAcg QC00;ïΐ}%]L /d]Ǜ%.R0vY\+wcza&+)+n>X;Y>3MsE0ʒxPj,*&CK;@Wk\ u{ K! uM$* 4*~|.X*f5L_頺ޅLp-P9`HB&Zȯn6 cvӎ6B27d8}iV0V0PØA5%0 ^TVTPζB/߲ ܨY_Ҫs=>aں ]n #~qțJFV ;B^^l#Cs dҵ4% c-SO2T}%le /?_WPcb (c1UGZy3=E]_{Pj6nߗ= ?|4'|ќwgȽ0xwU3ۘ:ZR89516\ir)ȶ{mzI00!9Q ۿ]]pwlvp܍xj;|KmP1fzWa]x]4dW Ra˧ IՊM6*ݜeٲx Yh%.v6>e!DZnܢTBBF6ـ 䗬ʩl:֖&֫pM3'WcD'/҃@9d|dnG<^Jeȳ e6OJR]6B5jUunʷ@E k4L{:0^~s Fx{Qh@Vb[QJBCe&Kw@BZ.Viު(4:#n=_$sxU!.z,T1JyjiCK&+R!jRaDC$S $6QkTmr%zR1^;}gca)ƌP.mkr:C-\W{囸iȇ*nT[Y0VNG ?;Q&|GC 7ҩv)^Q|ՏWJ;kRpvKiw4pdžSVVG_q ~HCI[٭!?o&>˗7SB4V) -d `p!: dg^6\4C ɸ>6J9R s0, 6Zx,7ڳQUcoн7+P+! ]foeXJ QB0D!o94ILOCMuY59hХT$wg"|N Y<>#Noeɇt`)F>KU8:2)6DPDFT%:7IejJyhVjW(~\FO4g<S=m{*ZșPE{,7`$D+Z/u1,h7S^]"=sx.{K^*> ߄p9Κ3_2o}q˭ z<<- [w8` ڑ`,-փDz[#\A܀gZ+$~1;Ba&h~.mfz).u݁T6:Sh]ziC4YS?#!֧ʉ\=\BΟ^5 h~Lƺ;QXƯ%~o͹^ٹju2D!R &U?pHh\DiT,\W͞{8D% !0v9>/%vvjwƨn!o(>܏E\{ ִՄU8[#AjFbX-+_3kws, XNyw4f#{eT ad{vAwd>FϲAcqQ&8Hbzn>Lgib/FQ|Pp+p.Fˎjyix͉trʵ'ǀh ;.cМsC{\7]A9k0γ!WRlNǺ=M}5 OM N~lۓ0GYI/NNGTyr._z%1we`< T]zڋm)mmdH(ЉE[k6=Z=VXEL[rx1ۧ`FI-5 U{ٖ gIOXرāZۼLp뢽#bݤ9C}\Vg5ug,(5Zx!F`)謌Q']6zj)aTA7Me]kvc~7X}z!'NC7[w!#) ?H_ xRc"k"ڜojl ! )3nd4G@ Cj}߇SYkHp)+҂:QtQG/{_G*yޕ QRO?kcBȀ $D^E#޹)[1JAT_Q t?;Lx4kBO@ҝi i'MK: '*}oEHѩoUgvL"[_/G`z؉D5TkSZk1&\ FsLcV&H8aF $V+ԋWnIjRCSP21Pǧn"t_c=*r'%j0!׾%Mݍ(sutˊF;R vULos":YspIk!8ͰLiV#ѝ?B@~JLѻu@;BwveÃϵ:ZU8nȌx&~VjM0|ZZpP3ܠ$"vWw 7uRt8q{a5.FD@5VMH5!(D3 R56a?wqf43*<-l>KFLR9?V