Overview
Request 199226 superseded
Resubmit with a more extensive changelog.
- 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
- Created by LarsMB
- In state superseded
- Superseded by 401796
- Open review for legal-auto
Request History
LarsMB created request
Resubmit with a more extensive changelog.
- 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 declined request
'Base:System/drbd' is the devel package, submission is from 'network:ha-clustering:Factory'
LarsMB added a reviewer
Please add a comment
factory-auto declined request
'Base:System/drbd' is the devel package, submission is from 'network:ha-clustering:Factory'
LarsMB added a reviewer
So even requests that are reopened with a comment are automatically declined? Wow, that is helpful. Why does the system even accept requests that it will then automatically decline?
Like I wrote, the devel project is also supposed to change. Does that mean I have to wait until the changedevelproject request is accepted?
factory-auto declined review
'Base:System/drbd' is the devel package, submission is from 'network:ha-clustering:Factory'
factory-auto declined request
'Base:System/drbd' is the devel package, submission is from 'network:ha-clustering:Factory'
superseded by 401796