drbd-9.0.30~1+git.10bee2d5-150400.3.4.1 >  A dp9|.󹮓+XLQJ2Q*S;kWn_'f@nIYr|t6<)X82z 7##{I=&Z H;˭)_һGN1z%|-ϖ;>'c?W0ZGj *b]J NQsќ:xa7,cJJxv?m7[ E+A×Qnc-c=2|VU(78s6ʋ̀ujeHD_OG'ntt'4a45da0e2d1b917a0e3d84223fabdf524e3e8276d03369f876827f3902b8a047d00c06ff9d17cc6e06ab916c289f65c5f3f9bffcdp9|d. 0_2ɺ+:&IРCmkÁh[\vWPksIHF,tC̐ 87O$B9_QbG݆+63+$ʜVqÇx+ʆp?|?ld * e$(48Qr      (<T(8 <9<:<BGGPHdIxXYZ[\]^#bc=defluv &hCdrbd9.0.30~1+git.10bee2d5150400.3.4.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.ds390zl31SUSE Linux Enterprise 15SUSE LLC GPL-2.0-or-laterhttps://www.suse.com/Unspecifiedhttps://drbd.linbit.com/linuxs390x~FFA큤A큤dd`nd`nc035ec1f6e8d1037c76810ac386110e1d29220f93e6b08d996e5c34ddb9375281ca3e8f71b7de618968e7ea9fe47822d9e704dc476aef8544033abedec355225servicerootrootrootrootrootrootrootrootrootrootdrbd-9.0.30~1+git.10bee2d5-150400.3.4.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.3a?=@`+_м@_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.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#1190359, update to 9.0.30 * fix a crash when drbd-9 node gets connected to a drbd-8.4 node, the regression was introduced between 9.0.25 and 9.0.26 * A improved approach to serialize rsyncs from multiple sources; the previous one could cause wrong accounting for online verify * fix a race condition that could cause resync operations to stall when the completion of one resync allows another one to proceed * fix a race condition that could cause an online verify operation to not terminate under specific conditions (corking enabled no other IO) * fix locking of drbd_devices idr that caused (very rarely) create/remove minor to fail - Add patch convert_to_blk_alloc_disk.patch (kernel b647ad024) - Remove patch Revert-drbd-serialize-syncs-from-multiple-sources.patch Remove patch drbd-fix-race-condition-resetting-resync_next_bit.patch Remove patch drbd-Fix-a-possible-NULL-deref-found-with-gcc-11-fan.patch Remove patch drbd-change-to-L_VERIFY_S-after-peer-is-L_VERIFY_T.patch Remove patch drbd-fix-termination-of-verify-with-stop-sector.patch Remove patch drbd-remove-device_to_minor.patch Remove patch drbd-use-DEFINE_MUTEX-insteadm-of-mutex_init.patch Remove patch drbd-Fix-locking-for-the-drbd_devices-idr.patch Remove patch drbd-fix-protocol-compatibility-with-drbd-8.4-state.patch - Disable rt build for x86_64 temporarily due to not kernel-rt still in 5.3.18- 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.30~1+git.10bee2d5-150400.3.4.19.0.30~1+git.10bee2d5-150400.3.4.19.0.30~1+git.10bee2d5rcdrbddrbdChangeLogdrbdCOPYING/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:28200/SUSE_SLE-15-SP4_Update/e70bfc9118a4e1728ef2230672e66868-drbd.SUSE_SLE-15-SP4_Updatecpioxz5s390x-suse-linuxdirectoryASCII textdrbd-utils9.2.0 utf-82678cd8326971b90d505faecaabac1daf044db584fbfca7307e3669fa27f8430?7zXZ !t/K ] cr$x#HC]8Y5& &uZtaMkJ].t%璍V{NQWMJ*zeĵo78 MKZ _i")sFb?h jޗy քVcwUAGt'1 Qm)=d!t^?$ˣpH(ߓKlg`&TOngƝe'AYZy. Gꄑ@'_;)=/p9SRNer9lLQΊ8^{,ѵtp bLMlZw0:ܔс3عsAiPOzMhI]zyzҴ]T$\V' H!&w\xxҬd\e?L8"OKzS|co>) :mdvߖ$@1Ze0Vg(vxK ; q^ 7 .'On$C.䑯uuQCqnw"nY,%GKCӞv6cW#@0߻gnH}1m5SeUCsuCWl2 4.ЮE '/9rQ0f$nPCc5 "!9\l7pk9MlVJp5sާe8qG٪{2]L ҙ p꒔סq ~4f!uefDnZ/zcTb%|Del2E$]43 tZs!ԝ4Nx? %%3{聺ՅL)  &r+>6E虽`JĻ#fK,Ʌ \Қ{z .է2U `*/–AJ座{A)tTe"Ψ? kB5Xmmњ+}Bi2ܑk^2y]Vx?nTsԊkWEΉM˥B7`0:ph1r (c*SK1ę܀$RYJ>ASN4mw>8sdA>${. Y!7 i1U[(Gȍ*%2r*̫3."uLD n ꋝP'=mC^Qf38 bKU̘oΊz-SHyzW$c-aэ9֯y*{>BҒSΦm&׿_nU(]W"8Y 6/ی6Bb .%~zG.s >+VTǝ }4)CWsc;7WW/A4\Q˧8SƃyQ,dck=-{ 5qTNգ2pz&, qBAdJźX i|U!-Pk8n*&a5y๓FN2HjAzRPKx;iׅt4EG>S+Nt#s7q~3Wݪ >ݽ* نwe:5=u}&w4;^׺o%[T:b/;3No2CU{=d 8\@,āʵk/ihKMbž"(ɹy:I /C?OA9 ΠUCfi Trtrʤ7*Vl3ˤ0zyM+q˼(!]MuuT%D57V:||c 0t@&2`=K MJYx` hw_9y%*87p+_a C~|j(AV E,o Qg6V|  4u`2 ; YH0SO6gQjk]T 1pxQr»Q:&Sb:4PN>1)d-085t| M7$WɫZb}֙.I&Y{UˮJ̙te.n`o ?9BÿG\nM: >aWRru^i'OPxzC 7X2u bY\zV֪R0Nwn 6?ѣM7 q4f=hEW5ԁʘfyQ3TiKXDpQ];.GJ3GӤ "wm* ֙{JD6U`;J>[2ϼG52^3e>E`-̀uOo' S;AϙszmeBcg `4}u&\+f^r:jasTt33>CcΦ)0܆^/[/҃$u!Xcwc>Q^.;O*6x Rk̅Rlfn(k*bK-;/vV/3"XOp$re!_:Gmi|4{7YIyڀ4>:RO8H$4.CRR $Flz{!vR4|<Ű&ad ?O1HWgC1P2+D[e7YN~o )F釨A'7+jYAcu5BAn6PA-[,rsBV;ÓwGWi_".;ߪ}0+%xGRXxP UsWS㳬ϼ#Z0~s0焅Y"Σ#ڮM6mNQh4C-˕Xb6 D@h[ $F欨jR>+`7Z3mߥIpsl`o-tӺ&\ P͊nq]K(ʛj|ub+"ƈߏh`W^!N`m@e쳺0w+A\Y OFoOàCpʿP& Oh;Bf2σsbv;xC=ư $s̨4?)$̆5~9Ldž#ʏ2|uJ?`y^ ̍r?lɠ2sN KX6@*Zsh.>#s55lgε!EI~4ؓbtc #Ziyc~F*|q:w5isPImEzY\k˨\PotiÈ*n|DZ\{W+ ESvr/jD1c1y_ : 컘V ^7[*ª(Q!HÞ,מ9p._?͢eV:9?nc%Ǣ[,#;Xl3oH[_ Xd &O%,oI@4&!AD1uOTl]{ot)<8 Ưx"[iaX `!Y#ѯy+Fu:x3hx}.3XC0յ7$ }(1b9-n#_EvP>AO^Edkad-/{;$BO.T%q~8rrDŶJqe hbEYyr:i-\̶zV\/f[14Ƌcr?W9o).SrLSf4gR^ĩ9p~}HQVE rfsH"S&`BOz]ly\TD8Vh'p": ƽS1e\`s+PqHO;Aۚ}1l"X:iZru#tL ~ f>VH3]O`uyV|jؾ=}n ϟnl;認?%JB9 ~v!4{|N|(ţR1$B#N= Weuge`:"8f [UU !PfCʌw%Vz g* Yo?߳B@fO y=,<;5;e#DlvZرG%XXBt:*=y508!.r6^2&A2;SxfGFM7'5M-˔o`&}O+L sew@PGQۦ(shUU&"G鑥n4tYY]egRnЊ늯i4a^ccE`Zg5}%xFȎ콐^G洊JEq+6!0!azEFR/Z̙'ڛ&qĎ9Tr -EZX7 FHOY+58Oy$) 91\ >6gg;`FKP rNE?N.u7q1Hg3e!٪wS /*c9"l6h)NlRZ^v<JPj(  xW7^)jsipHgnʖՓb5tq pgiVz0rdz(kZ.4m,6,*zDϩncJuGqakY8 Yv *vဠ@<1Q *Qڮ7g.%\!(>MU0mEBwWZ\`u9þ(+Se!pkv6$I>2TuO6(e琢L6\|#-I[hGۘ ۺ,v],t.m7uѨm\UZy|sGkHJڗ$+L3CW= F{J@.GW/lAj|?,isȃL BOT,.6J}_rNlԧ ^>&(~rm}d`B7]Q9 bbpzmOAP˫叫Np/Eԍ1rT6 9ܘ6CF(?%NQk9pN(td`FV|N_ a"RKSfe4$۳pk0`˟HH Mh QY`C0$;)1sU~:S)Et3F&+_äkr@&׺.k#8OBzsդ5⏪?͟H]93 4s^ kz}'u˚]xN0Os tv,m+UKogU2!Ȋ߉u$EHYrEH};U4߇o_k珰v !+׻sH 8 (^5i$Kq\c^Qa&a?,L$l/6X` Ǹ ;KXRpdXph7CcÒ{=<oE J=Npr!^4GFrTTD|eMr4:_ױϋөO;Pƒ_~"Jp4P;#r-(< /t7]-X| 36߫Ԭ92,&>>>N\HӼ| wDG]}+ 0GޒIc Td:Ncyc Biw[_9ھޠ@i8vE\9ubB3kFuHyq@8(:*yX%/dO JTL 4XNXbD wD$;V ֿknovϘ3r[<I֔%9rkfTbB)֭3]DZָԀofڒP nY [b$`>*`6je1[JIP=cmܥ=Wl 2)&;xJZí_GqNUпeITr>Pj'S).B)b `&yUNaa:EbVQ M&yM L@ ^cbjWIEçvUŏ Bjr7N2Iw%^h?c T/wZ:>WͥQzآ/}*p6I0oy"ܝt5SJڎc]6KWB Q`/+@LlD<4iŵhJ-[&Mz*x_W!iɜ=Jk(ݻ}{Tk׫А2*2Jg KwVO/T Rα9Iy{#ګbU=ՠc$Pc^6 Qp/8IvqF`5u\ 5554ۙU+ƐW^+ XT6fsE@o"Hfq[axQKH l}F"y[2]7L.?i0R?+*O6:冒IEcz&s} qXSŠ q.l8Vyjh U#/\M *gq2XNٚ36=ׁ9XI!ne_vHouu3u'}a( 0q1e#iA_.֍]k3:G.EIGNHAYHϗoyE;Sjy>o ݪ[q+лY*|Vn$Z @}`spnSG s~9\U[g<6r]P>mjO RP:(ȁku녉=YE) ϱ}!|$P >$0jj "W䈀;ܚQ~(Q.s/l!A)(xy\IײYxA5tm@ ˩#VPaNI⨃Z p^Yh&[`D(ywqp1"ie&ps *=P" xxDՎq穰PN :,8D`nC>k*:J 莥жEf. +ܟwU4p.Jw *_긡9Hlq|`jEiXr8m{o<-4 gDʩL# }">_}B}'T)~J^Q2}?qMNMOd+yƚp/)I:5^bGpe Ja6Ka[N&-p*jLMKgPJ;yVu(yӹXQ q/KksH򺴐aV C3ql|#c{DY?eŗٷ!ҰˉLC81ye:3DoNq 0}p׃}\F=)+?2Q؜ּk:FNAu) j$nc hl۩skYƝ0%7FP%ma*ï*FY>R^σ"ɅZ&:sv_oHkp!P`0.0l:,|Sn1oBI"$^,R!3`Áɴٵ۵lQ }!ܳx$h5]ٍz*M0K+B(}+!\,qx(@QZ xi'EZH92<-^03ZC/1&z4e*8L-,ڊuJw^~+k @ԍhR K)Q]wH"/>0G?7C E$}~{ Zu6 [pSA.m+#9yBnϨF(7&[4_V#Ƽ{.yzbI nJi15a`NƦ*Q|" * al.xS60n]D0R4QZYLI/@^ jBg~4ɞ&й?]\ě(VYM"3ځ`/9K4dߚQAkK)%pf@0i˺i/|pC7BhFuDy6o2ӑ6Xo? fB#d=cnZY܌MfWԜ[p5/Fj[\mciUS0ą':@Q-,n(볔r5 8JKmL(E5ɜoN[$n0ZGR߄1V$ܖd'SKb`̚jŃ=GvBi ati>4⭩iŁ2eP2#_C9,OL/ς .D5/_<7?5FvdY B Cm* nm>g{X.Lȁ&aB_J _$cHj_%Om<.-wq*ŋg[`/!6= z"P;|,GM] 0[Mе9-0"57&HHͥ5T("j^z .U4yyCHTeWNym- ~%_Kt18W2Zn1Lso 3[wan, ކt(]5QӸ@!4€:gtEjHjT4Lh:`2T:IqKmti0Q9;:Rf{8bN(e{dA]t|QĪ%~tq>GC gHk9K.AB0>3߇e@pww!=nԇOT{OW0`+8:`т93~AV5{aRCjYrG-sȟ)㊘dPv_v\+֪k:k允t"۪H{-qO,eQm+`IǵiwA+U~]O޾v*j wn6WDl³ȑWeuw- "`s^G璞4o-'%nL.{0ěm5ăC Hq5T,: pUNK.R ەгUL#Sꆭ:y%xvCGZ$DB$Xe4>0>V\KUsIC= >8Tzadp<(µ˳O_{Xe7/~Uۊ&U/P-"wD;bơrMl:AKrtVw[\!当WZ(8fT=VAm0&i3%64 coހU57OI{ !oW0=Sjp594OCu[ܹ 6ntf)`~jaΠa`(~DH䬒J>,K/fCo|Z0Ƿp~ kh>*,g<[~kt4<ꮥis/?E|Wq$_|EYwMXtXok|(=x2K΀Vz~c '0֖oWDe {E}݅n1Cjр>XxXI>ȹt.99I}śYL=leTAwD,_v\D?af2y0`RaU&]U._7HZ|%T .nR̡P+ 2 џO.5,qhТDrL> P٢Cq|jI 3/߽ ,n.fV_><;X=LÖ""WGHgF2%eV Ӄ|RFyyf?2q/z PԹ+%~$3:!{p:M)K:π҉6- M!uxQ%_~+k /\&W"C[5W6^]3qX2%:> M76U,hO/NNBhO"S1Ɣ-%ݮ%mɰp%,)#}V崡ҭQ8mmk 34$>vzJJUF)s'bMRa Y6%!NuDM0jcSvA7b"b0el ~82f&`֌G ׸ 3k oαsAT-C<100>H- w4\IǮcd?Y(_QghUuB]ڡW|s˞o6iIo fPT?H[~, :!囌C:>7Bd񟱁Eղ!4T|_ҋv]7֠NoU(6}JD|VR$` [- `~IΝaKW=93 0(Hdr%Mn0&UzNaQ$B!8b5!smPg,Iamxo k#`'ec.ҀUI%Y{> V||:b֨ Z4+L/&vX5nVXq; >RF&G\ya`rHʫ$P1~{r;5+PHUǥo͙o#YqArG eSxwsh@1V@))X3բ-2 M`#w;;6H$F^zlPbkd}G9KN^ksVP "/Y?WPE  4\ֱ4zVA=@8b(\F>UY'+z3)Iڷ[vڃY-{đ6mrYZPyz_fϸR%g8T-fR;i'ab@L kyHc'S0p(ΧV:o{m*(#fS;Lol ppAN^a`ѰRY_Ҋ?PF~ v ڏ%I˯P0-ʳ}5Cehv?5Ajr"!$Y_zb #NDsTi,/p3;m#)PzF8y-Ith}8ƲZUdidxM.L>>NȥI N <Ō=&eM+3 F+4Fr,R+FK E9Ճ9.1;H4QM*:BCN,>>|EMoaްa[o%T(gMDٵh! -cgbmq?W{jjr8ir AgCBVm y'LDo j,8F@uO; fv\TQ4kȊI̅H%hN㛊)3{hS&t.`%}` 5qGqGg*O֊ɢg|wt T]V+n7P7.JJs"UIbDo-^rmPtkr@{Uc~yO׌DN2и?II+*mYZ0%lxJVcGL*T6b]ƕF뒬g o4I$BCR, 1aRf i2+!b;7O&y-뼏`ՠ.ڰv)DQ RzF9AG5 H: !/`5 Zꒋ+j^BUw\Rf@X /DH_9lر^ɥayAFp+ŷy`cv6R:()h_6 02K0(#[{ k> {n~EP<'k//āo?J.Ñniݘ*Ց x5rƐ#dʋ9!_'SsBFT>s}S`epZ,XF!1*IRYˌ>r֩#d}4IeJFYJolYy*^G?jj_OýlM[!6ٳ0|V>"xR1!Se[5QL1?FIJ_Z,UƇCY]ҷX؈ju̞A[-U>Gvט>T?ђv^Tr|K) v8w'Qf00l xrgD6 bfyVm_?RXPi~uI  &R7q&ݝ`f\`2/w*tcMf͉צ2؇;UP9o ¸_jAm8Zɉf WtKV%[>fbVVЇGqzEۺ=nh/|#l)O;JZrŸ|囷VƖ!zٞ\ ~x݋ծYUY:ت*3?I"C5+FDfm{~ƪ7yq4ƜM,*X5.R_ط0U=^\NcW*ǝ}%zfĒR1"4W.y{!pW(fFF` ^\\ ]\p 3؄@i5tMe9HM"b:D5{bOhG1&({K OSxc!U=c,yO|C"Ҷ FtN3#).oOw乏aPHG.!j p(XBndnכ5[ȉyM d~M,=@oxӳeǖGwf16 5 i|R*'?2`QJb ׀x.(1s1q QguP4&tt\{ae+xPm*lr?H.ɼs2˛.cnxvRxB({Z;ʃ{ @<2m eD]X.<F.|+Nsp׾mJn@ApÕHB0cP1 6Bh~h\Z R(}7<*MYpFK#͜˹IQu ×y@fRo~܇u7'?q1Dd% ?|;d2Ae6h!HƘKkLw7x}6c8a|7&Z-+Mœا:xPvЭ `qj' ʶ}UDkGG%a}/]z6rEd*G󎫋t]] v[Ao7:5QLD @Jf8ЇpNl;s?bcR:*n_É_dyj &Ij}v/Df"d~kE/(pje!hqS™9+S/P@')`>JhN2LzxGH?+r d:8?abυS5=KDڎ/L:2+izZ* b}O=7[E־aiv,fTc䃤&Jt*)pcxkTڨ+t+oQ`Ɋ YZ