On Fri, Sep 30, 2022 at 4:56 PM Pete Zaitcev <zaitcev@redhat.com> wrote:

Unfortunately, I'm not familiar with the exact details of this.
There was a window where depending on how linker worked, our
code could get linked with an incorrect zlib crc routine randomly.


# When upgrading from liberasurecode<=1.5.0, you may want to continue writing
# legacy CRCs until all nodes are upgraded and capabale of reading fragments
# with zlib CRCs. liberasurecode>=1.6.2 checks for the environment variable
# LIBERASURECODE_WRITE_LEGACY_CRC; if set (value doesn't matter), it will use
# its legacy CRC. Set this option to true or false to ensure the environment
# variable is or is not set. Leave the option blank or absent to not touch
# the environment (default). For more information, see
# https://bugs.launchpad.net/liberasurecode/+bug/1886088
# write_legacy_ec_crc =

https://github.com/NVIDIA/swift/blob/master/etc/proxy-server.conf-sample#L326-L334

set it in your object-server [DEFAULT] confs too

--
Clay Gerrard