Overview

Request 199486 superseded

Now with the changed devel project again - for 13.1 beta1.

- Update to drbd 8.4.4rc1
- Disable heartbeat support (heartbeat no longer ships on openSUSE)
- fix decoding of bitmap vli rle for device sizes > 64 TB
- fix for deadlock when using automatic split-brain-recovery
- only fail empty flushes if no good data is reachable
- avoid to shrink max_bio_size due to peer re-configuration
- fix resume-io after reconnect with broken fence-peer handler
- fencing script improvements
- Fixed attaching to disks with fixed size external meta-data (This
regressions was introduced with 8.4.3)
- Allow online changing of al-stripes and al-stripe-size with the resize
command
- drbdadm adjust now deals with IP-address changes correctly
- Align the internal object model with drbd-9.0 (away from drbd-8.3)
- Do not end up in Unconnected state if the connection breaks at a
certain point during the handshake (was introduced with 8.3.12)
- Closed a race condition between promoting and connection handshake,
that could lead to an inconsistent view of the peer's UUIDS
- Fixed a race condition that could lead to a full sync, if connection
breaks at a certain point while starting a regular resync
- Fixed crm-fence-peer.sh for pacemaker 1.1.8
- Fixed a list corruption for read requests that complete with an error
after they were aborted
- Fixed a kernel panic if the device size was an exact multiple of
128MiB
- Fixed a potential memory allocation during deadlock online resize
- Improve the handling of read-errors: Make sure that sectors that had a
read error are overwritten with data from the peer on the next resync
- Expose the data-generation-uuids through /sys/block/drbdXX/drbd/
- The new flag --peer-max-bio-size for drbdmeta create-md is of use if

Loading...
Request History
Lars Marowsky-Bree's avatar

LarsMB created request

Now with the changed devel project again - for 13.1 beta1.

- Update to drbd 8.4.4rc1
- Disable heartbeat support (heartbeat no longer ships on openSUSE)
- fix decoding of bitmap vli rle for device sizes > 64 TB
- fix for deadlock when using automatic split-brain-recovery
- only fail empty flushes if no good data is reachable
- avoid to shrink max_bio_size due to peer re-configuration
- fix resume-io after reconnect with broken fence-peer handler
- fencing script improvements
- Fixed attaching to disks with fixed size external meta-data (This
regressions was introduced with 8.4.3)
- Allow online changing of al-stripes and al-stripe-size with the resize
command
- drbdadm adjust now deals with IP-address changes correctly
- Align the internal object model with drbd-9.0 (away from drbd-8.3)
- Do not end up in Unconnected state if the connection breaks at a
certain point during the handshake (was introduced with 8.3.12)
- Closed a race condition between promoting and connection handshake,
that could lead to an inconsistent view of the peer's UUIDS
- Fixed a race condition that could lead to a full sync, if connection
breaks at a certain point while starting a regular resync
- Fixed crm-fence-peer.sh for pacemaker 1.1.8
- Fixed a list corruption for read requests that complete with an error
after they were aborted
- Fixed a kernel panic if the device size was an exact multiple of
128MiB
- Fixed a potential memory allocation during deadlock online resize
- Improve the handling of read-errors: Make sure that sectors that had a
read error are overwritten with data from the peer on the next resync
- Expose the data-generation-uuids through /sys/block/drbdXX/drbd/
- The new flag --peer-max-bio-size for drbdmeta create-md is of use if


Factory Auto's avatar

factory-auto accepted review

Check script succeeded


Factory Auto's avatar

factory-auto added a reviewer

Please review sources


Factory Auto's avatar

factory-auto added a reviewer

Please review build success


Saul Goodman's avatar

licensedigger accepted review

{"approve": "preliminary, version number changed"}


Michal Vyskocil's avatar

mvyskocil declined review

Hi Lars,

please fix the version - the 8.4.4rc1 will be considered as newer than 8.4.4 by rpm, so package won't be updated to 8.4.4.

The best you can do is 8.4.4~rc1, however this does not work on older rpms, so you'd limit the build for Factory and probably 12.3 only.

If you need package to be usable on older distros, then use something like 8.4.3.rc1 or 8.4.3.91.

BTW: Check output zypper vcmp 8.4.4 8.4.4rc1 - this will tell you which version string is considered as older or newer by zypper/rpm.


Michal Vyskocil's avatar

mvyskocil declined request

Hi Lars,

please fix the version - the 8.4.4rc1 will be considered as newer than 8.4.4 by rpm, so package won't be updated to 8.4.4.

The best you can do is 8.4.4~rc1, however this does not work on older rpms, so you'd limit the build for Factory and probably 12.3 only.

If you need package to be usable on older distros, then use something like 8.4.3.rc1 or 8.4.3.91.

BTW: Check output zypper vcmp 8.4.4 8.4.4rc1 - this will tell you which version string is considered as older or newer by zypper/rpm.


nick wang's avatar

wanghaisu superseded request

superseded by 401796

openSUSE Build Service is sponsored by