<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="135">
<package pkgid="e1e9a316f6a1368b0849c5a02a3d7f71ce9dc755cc0fefa8ab45b506eae97b66" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="899ffb1303d8e2f628ffec1336f8452c1859e6b19e939a8cab48c8717e040c11" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="00ac8679a0de733be31f1e74969038b3e784c6b67929af67227b876defef45f7" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="01e3792abbf26e60a9005a042eab02fb0e2c2e3c823578a523c3b357698a1000" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="2671b78b12ba9163850e9577b56a7e4f8833de731aeb6d6805a4677dd01d3327" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="e5c8afdb3d735b480449b376912330e1d7bf57c43df05f23e9dc71842cd2bf26" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="cc6c75669a13c82f8f048c68524fbce96d135168d18e3a9b0c6a1f9610aff68d" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="4fc0381a5d7d433f3531c7118df3535bbdae9dfbe573727a0490dcebadf8546f" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="b930b3c26d8f2a78c2a56261d94bd88317d71a50673d182b54054e4b5ce21984" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="4502a5e6f78f40bea351c157b9c101ee7dac6ba7f29e2d8f413438d196fe02c1" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="ce1738d1a9e955cfd3c502b9351bf12c0a8bda9566c7014d10df8d58abc7d152" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="1e345148e2ec9e208859b1950500f4dc827c5f338aa621358258d8cfb210a04d" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="1aa595f0890d7d68fb07a3c820222044a27b7df7b1b3b94784839b1682987d0b" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="a4369701d31f800321a4120ba151ff3c09b95410e05cf47657ba8bcbc68cff33" name="libquobyte" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="49321d29be44a17f62dc920cd7e1c0fd3044a74d5b2bd6269f58af2e8d701afe" name="libquobyte" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="2209e9e8d880ec5143026d04f25b1fb8e5698257069c101703b0d11f972c1386" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="49620a902f425a9faded647784107887338dcc27c792474e250efdc48dbe0e0b" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="c537f148a257b2161ccff043ac354217d58c3f71a76cf3a0eac465abadf20eb9" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="c8d9c2a4b4548614a5a3aacdd7fb17236fb7183b8d1c8c4243d9f29293f3e06d" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="769570051b828c790546fc344e1af749f7ab10537c81987feabe7d90b8af9ba1" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="03d558af8d1319b1cdd22e5f049e79c93e4b09be281a51ae95b9aae28d1bd41e" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="1b226a51dbb350077d8efbc905d6aea36df97a30f7aede77847293c2596afaea" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="c01985493d08e8421804a7ad8ff753dc477c51be9a1915079a1b9abba272c2d4" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="dc5fc5e616b28e9424f7de1dd8031281ed44c6637482b1572700bf21105da39a" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="157647ae1d47004dead644fd816a384e7ef1a1ca85273c52a9f672ede15d70dc" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="ddd73c415febf427d5c4e9d8d01e56df9bbfb32856d808593e3ffbabf2d242b2" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="19292edb823604d04a63bd3ef7c809f39e48df9d365f72a3e8029e792fd7ae2d" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="5d0928ea140f02691cf533410d8e47325748ac5cf348429d1e6254e37f72da05" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="35141510c6cc840e17896273d19323ea658d9dac62cdf6dc55278ac64ba2e9a6" name="libquobyte-devel" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="64c971e0274c96d74ae1f11adc41c955d2317edb6ea124048e12460456b4477d" name="libquobyte-devel" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="9085bab6cd45df96fcf1e7de2f1e2d7995e00156926d3f1bd8fd81702d784a50" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="533f07637adc64cb0c90b4758cf850fb95c18ad517ab292c737a9b43f75bae14" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="9315b55ce0c2410d6bc8737275f8fa4163d0e83d0356b2de543af1e46667dbe7" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="0cd752fa34834a611d6b14226bbfda3f26216e614f43e5651f73517d5a6184eb" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="a5f06677013e8e2f519b370438e50c333a1d23adfd6a26bad75218c20605dc0a" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="5196b82deedaad9edce53801f1fc663f57a2b0b8a52fb29a76d5948065f6b54e" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="1491298a4a19abf6179076a54128de2e4d1ed2fb9c9170b55b4e305ad01d4d50" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="36310a1a18c1917236b3fc4421341c0ade0e309358029a5fc8a7e1f888e81db8" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="b0185d4bd6d7a30cf92d5cc5cf9f40a6efbecac171598ae262422d68786b90e6" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="f584e41b688212da267a5d15d1c83e031a94006b28a1c082e571ed690715f471" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="6c614b76e58a69cdef5ab8ed0d7c7181264fe15424ba0671417b7ce1af4294fa" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="3b7a582f4626c872f28d50315138a94abc128b2a8f8da20c1ccb70027ab2fc4f" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="b9a1b83142be72f27c3be0429849b20945099de4a28761bd2b681c0306252655" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="570beae966f64d56bd8c0114183fe4ff1588c2d39e6829ff8247b92d124ab9cf" name="quobyte-client" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="b6ea3aa78806dc6172d78e8f25543b6135f6051737fbf5140353302d53743502" name="quobyte-client" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="d54428a02db27de48eeda9934f3d1c2c74baf52dbb49dd5253123df227d6967c" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="df44b93ee8bd44fe3931953bf153d63439e3e36723ed2d6028f61b726b75aa60" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="888aed88381f933c22eabf8538dc24a6ec5f6ad1c91730f8e84535a6f4d44430" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="af307fc8a409d290f84074e8445ceafe1edd1017371432e034837769fcf1f352" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="e25569bff3a714cebbd31d392ed5a1e26b14907a6932400ba58132e794757dc7" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="b0c3e048e5be8bb5626320a047321ff5591be3b3dd5623a3e5ea30663b929b8c" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="69f8a5f2d8eecf186c9307a57d68550c43735736105c97143fa7c23f91bba6d1" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="88170bcc683fe6cbe439fae4d9a5a5e3f03d3bdb073711b6084b5b2b2b7bf2e4" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="e057bc01119eff38b0f16e061d948418bf13a063b5d7314e30824bff28352ce0" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="d81d033b40e151d093a3a37a2f8f52ffa05a50121d2c219b16794c0f59c16dea" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="d436afd67de5de17f37dc6dc3b020b96b0401171de252a8994f1cc237a000e76" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="9d3f604dffefe455c080f01fb1ff3448d49ff8cedc4b0e5b33c9b41841e3bdee" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="a63a70f429b03bd32db58d5ca4785a4a429cc69010f018463f8ab7de9e59e080" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="3a4f7c3247b7a4f3f0c98e41858f6a73cbad82dc53dd5b9ea0c5510bc8d3f4cc" name="quobyte-client-tracepoints" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="5d5fc22d2483b4bb8c1aff0bd3fbd250d37eaf6d3326f4baf1ef83d6f86d4b99" name="quobyte-client-tracepoints" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="653d715707addb82d9790e1ff155d8274e94472cb406dd32b6f7aae28e957f9a" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="d867d83d18a915fa2048728435e08b1f915ab8c8a8f4124d18b62c74b3f9b03b" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="4f326b7847c25258aa62d06160814cd5981dc5bbf9f8451997f34b61b6e00642" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="aafb2fcf84feab504f2b32039f6cdedb14d984a2108542105e462f3271fad62f" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="c7f4e1d0ef22d2530b54f00bb57dc304671f5888a1120d4910066b2968a7f8a9" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="4755e01e3ec730b52e415d1020374a0c10315ae94727ba1e1a471d6dbc428125" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="2774e547a7da453bdf0af5aec9009b481292ac26ad52fdbe6921c0e90b70e3a6" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="03bd3a4a615dd138c01d907d473cec9e707e2279c808cb88edc9e3d1db1b61d3" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="fe398cf34ae520df0edbc1bcb2a58ca136db1cf02b77b40a879158e26832c9f9" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="001101a4bfc271cdf00d9591831ce05f623c7b69958706f462b39433a530f95f" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="98eb97c60cec204895b2ed537a5a6d8d7b6e75664c1a15d1ec86b38c4ec1ff51" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="faa3c3316d33210e9c277a5795d3954025d4948985082dcf0de449e9a4bbf40d" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="b39d24d5569f9c14db99513b64b5fe1995af0799d2a61716a339b1a6a3eec251" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="9063392de3439bf8653ce0f6e011e5399f15c2370008743794643c9954f76f11" name="quobyte-hadoop" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="2a1e438dbc8ffddcfeed1d4428b0eecfb827b0b7fa09d04c7dbd1ce0d08826a5" name="quobyte-hadoop" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="0b6d314b98c650501e9a84a4269db965ea8c9da6fe0431cc517daaf7e7bc0e7c" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="46fc45c65e8db9c4953a440ebe196db55253b9c96ba4f7ba7a2a83604f11d729" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="42412fd4fd184154cd917260d2353371faa5c646b10bcafeb73251a920176e26" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="1c82b67757d38b8458917823ea35c43fabe03162cdde2da8f29cd75d2c68d438" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="4501d10418fe1793887296369dc37566c94f7ff1aacf4fded7a150714a99570e" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="bc563f1e6a7f53f8768b3d7402c653897e5c01ba63fab81d65122e71ee1b4691" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="9d5eb583e491513f08c378ccd07fa052c59e26f4bd40dddcd20a12be93b10d34" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="780475359b969db903b3e55411abadb318b287855c612990c97248dc1ff62e8a" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="cd1febc4d8fea874fce512a30ba333e17ba8acb9ad22a0c6ba08a47dda8eef12" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="2bc4520e27b42b4f1e4110ee31074bf158bd3d2399dc9fa6bfeea4d4cb94214b" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="0e031d9700f81d1ceef7abe228f7490266047695a5a87feb546ccb495aedbc86" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="007796fe20dae59ba817c7f803623a7379534d52a4eaa314c8958a7669986200" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="cc2ed4742991f9efa8f5cecd636bf165370240bb9377cedfc6f29471ad45e6b0" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="50ad8e4fb31711be4727382387a0d3384ad25db01817a3b5fd7b486a0b253116" name="quobyte-nfs" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="48ee6494b03ce06ccfc2695abc8148d83e723e04a10891702f8ce809558fe113" name="quobyte-nfs" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="65c9397e7839c2089181766a19da240e91b8cdafd28381cfcfae8759d57eed3d" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="80f660dad87f91916ae0b01f354de55b62982843655044ca3e193ad404b52dcf" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="7100e1a8f0bf2a5e6174dd1c59c0ef87bcb152e36d1bf2fca6be94373040f7e1" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="57a391a601d64de1d0cdf3065a5b284daace269a6b0c3bc0e65ead96e967968e" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="24bab6cd8ade4f84a711f27dd7603157a0b300d46955ba582b8e308a17df39e0" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="7fb99558b4bc9b3743c54f375e165ad2e1f3b55a9fd130f9d692b119260f1706" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="d1764fedc59b73f91f9f5ffad7195802249c44850fc35abe01420a22944b68d2" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="3ffa6b2281a00c6ce137486594a49c63b5d83438d1882f077c50395e8a007347" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="5d84608fec1ffd43c7d683187b90983fdea30db67516b6d19066d5504f9be227" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="43a653647a4200fd30306b272dc4ec3d6ff8be5314e36cae2b6c931477b0129b" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="83c2f7baf7b13f60ba43fe27b3e1d6b097bf45134fac213e18413bce2844a022" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="d6c77da87100a131b1997a2e7efb0ba1a7db1a438a45949ecfeb858d446eff2b" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="f1a78fe4beeea8b83e91c89d0d5fc43047cd7a7daae07e99398f7a48871e2b40" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="95d091835445fcdb0e744540fb069e98a712da0a6d86eb8c7afd28a5d61bbf3c" name="quobyte-server" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="0ab03e6dbb3d35daa85ab8f1d8097b4e83d7719fabe11504daf469ccc9b436dc" name="quobyte-server" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="c7f2087f498e6b2b021e6970d857f9bbb67042f443f350b77e1bc99e9f000633" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="27db619d625f43e55de6155f9968f609668f86e7e418966a6cdc00cf99596f49" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="10446ba53e32b21d373dabfe292e305c82708e8fd35e0c8287db70f826475a54" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="c9e45c656396568cd811afac4b2e6c66faf1c3d448bbd332f8d0063044befb6b" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="95782c39aaaf0fc4ba214a38ddc9f80fe76e4c727576f4076e7af7d4653947ac" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="8424e2c0b7e63e26a735de403625a9e0caeeb6f5a1ebf2ce54b7e57aee0ea34f" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="04438100c796450bf25bf1324524e817da68ad48102aa63118b71e87fa07909f" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="43cf8c3b078ca823dca378f8fde4ac3426b0d69193f2600f724bab216b695357" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="5768cd2892a1d8fd44abc21fa97345a671b9f1a2b8c982aa4828be96c2ef0237" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="70a318364e458915885f264a0df5cd69090fadcc27a9c30e08fa412f4cb191ab" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="7123c78c2d48d9a135d3e940170550335ab4380b131a7a1d153ae239ec2f919c" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="7626c54488e8e16db09f2b9c79a06785ca78a20cdf43d4d06f17cce386136681" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="4c3eb219cfe674dd2eb7bb29e3c964aadbb75842f23e6f7969fd0ea637e9bb29" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="d92a47428f93dd9d9f02d8bbd03d56e2852ca4db3a90804dc36057345e7fec75" name="quobyte-thirdparty-libraries" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="601908144c0e34a375de9bed17eff0afae0e5097c7dcff5674a74b506fca215c" name="quobyte-thirdparty-libraries" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="73bc8b8d02ec9fd15cb88883a4dab4b895e2f66f403321065e7bab6356980106" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="3.25" rel="1.1"/>
  <changelog author="Quobyte Inc 3.25" date="1740052800">.. Release Notes for 4fbbd59204bda653f2ec9266ad34f704f8e36d6d

================
Release 3.25
================


.. _Release Notes_3.25_Registry Service:

Registry Service
----------------

- Fixed a scalability performance issue on registering thousands of clients at a time.

- Fixed a null pointer error when requesting quota information for a non-existing volume with qmgmgt or the webconsole.

- Fixed an issue with clients not getting notified on certificate changes affecting volume access.


.. _Release Notes_3.25_Metadata Service:

Metadata Service
----------------

- Added accounting information for files with delete_after flag, which will trigger an automated recomputation of volume accounting information through Reacount Volume tasks.

- Fixed a regression introduced with release 3.22, causing Metadata Service crashes on scrub tasks reporting files with DATA_LOSS.

- Fixed a potential stack overflow error when using the query engine to resolve absolute paths.

- Fixed an issue that caused files to be falsely marked as lost with invalid file size.

- The File Query Engine name_extension attribute no longer matches on file names that start with a dot.

- Fixed a bug that could have caused tasks to get stuck on erasure coded files.

- User-defined S3 object metadata can now be queried homogeneously without the s3.x-amz-meta prefix.


.. _Release Notes_3.25_Data Service:

Data Service
------------

- Fixed a rare Data Service crash bug, triggered by a rebalance maintenance task if processing a file that cannot be put to an alternative device location.

- Fixed an issue causing ConcurrentModificationException errors on file truncate operations with concurrent writes.

- Improved single stream performance for reading and writing files on NVMe devices.


.. _Release Notes_3.25_Client / NFS Gateway / libquobyte:

Client / NFS Gateway / libquobyte
---------------------------------

- Fix "tail -f" to work properly even if the file had been opened for writing.

- Fixed unbounded memory consumption of the Windows client in case of many buffered random writes to the same file.

- Fixed a bug that caused "stuck RPC" alerts to fire until Client restart if they were triggered by a streaming RPC that have been introduced with 3.24.

- Fixed a potential assertion to trigger with message !ec_lease_holder_.HasLease() when accessing erasure coded files.

- Fix access to EC files potentially get blocked if some data services consistently took several seconds to respond.


.. _Release Notes_3.25_S3 Gateway:

S3 Gateway
----------

- Fixed a rare bug in ListObjects. Before fix, listing prefix that contained "&amp;" resulted in SignatureMismatch.


.. _Release Notes_3.25_UI / API / CLI:

UI / API / CLI
--------------

- Improved the readability of numbers on the Webconsole graphs.

- Fixed a regression introduced with release 3.24, causing removal of the Tiering policy on saving of the Health Manager configuration in the Webconsole for cases, in which no Recode or Retention Cleanup policies were set.

- Fixed an issue with license SYSTEM quota information not being available immediately after primary registry election, but with a delay of up to 15 minutes instead.

- Query engine now supports IN operator for lists of strings.


.. _Release Notes_3.25_Other:

Other
-----

- Quobyte container images now contain the required libraries to use RDMA.

- Fixed a bug in quobyte_init_ca script that was causing service crashes with a newly generated CA.</changelog>
</package>
<package pkgid="0e905b89684bb03f13f61ea20f47b7b36f372f5bc3235e7acba2ca6926f9bd18" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="5ef368aa028135e44ce3e48e4be15783864b99d97a0685f564820fe4b73723d1" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.4" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.4-1" date="1754049600">- Merge metrics in Prometheus metrics export to fix "Error on ingesting samples..." error.
- Adds retries in NFS virtual IP timeout handling on transaction collisions.
- Rebalance Data device tasks won't delete files from defective devices in mode DRAIN anymore.
- Fixed an issue that occured when writing to EC files with particular patterns while data devices were unavailable.
- Fixed a regression introduced with 4.0 that caused operations on read-write files handles to hang if a read-only file handle was already open.
- Fixed a regression, introduced in version 4.3, that caused the missing task progress data in the UI.
- Fixed a bug in qmgmt files move command that caused task submission failures.
- Delete files task is scheduled without waiting for in progress high priority task to finish.</changelog>
</package>
<package pkgid="5e7566fb06eb02e4a9f27e5e0a93d34792d569fb86bf68162748989e67a158d9" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="1e8b1b7a625706f37aee4e2b9e95b3c5da9612fb6aef4514e7720685360f827f" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.5" rel="1.1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.5-1" date="1756382400">- Detect cgroup settings that are larger than physical memory.
- Improved LDAP client functionality for user's primary group detection.
- Fix configuration of Metadata change stream publisher (Apache Kafka).
- Fixed deletion of NFS virtual IP groups.
- Cleanup Volume task to handle missing root directory metadata entries for legacy volumes created prior to release 3.0.
- Changed a policy for the move files task that caused delayed reduction of accounting for the moved files. With the change, any concurrent operations on the files that are being moved may result in errors.
- Fixed a bug where file replica resets issued by maintenance tasks may block each other when started coordinated at many devices at once.
- Fixed renew virtual IP lease.
- Registry and NFS gateway now pick up changed virtual IP configuration immediately (no restarts required)
- Fixed an issue reading from encrypted erasure coded files on clusters with unavailable devices that has been introduced with release 4.3. Files created with an older client version could have returned wrong data at the end of the file, if the overall file size exceeded a full object row (typically 25MB or more) under the aforementioned  circumstances.
- GetObject API now supports suffix ranges. For example, Range: bytes=-1000 returns the last 1000 bytes of an object.
- Fixed a qmgmt issue that prevented quota creation for the "HDD_LOGICAL_DISK_SPACE" and "SSD_PHYSICAL_DISK_SPACE" resource types.</changelog>
</package>
<package pkgid="981250826eba28e4f8231b1884d59a11c03219da0dfa19167756017ae6ebe47f" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="f17e6daddd6692e24f694350ffcc1da6aebdf720ce69c648db501e9a21a68b7b" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.6" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6-1" date="1764244800">- Attention: This release (4.6) will be the final release that will run with Java 11 VMs. You will have to install and set up Java 17 before rolling out version 4.7 or later. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
- Version 4.3 introduced a bug that could cause incorrect data reads in older (pre-4.3) encrypted erasure coded files when devices were unavailable. Release 4.5 mitigated this risk with a dynamic runtime detection fix. Version 4.6 now introduces a permanent solution via the new 
- &lt;title_reference&gt;CONVERT_FILES&lt;/title_reference&gt;
- CONVERT_FILES
-  task. All customers using encrypted erasure coded files must run this task to migrate affected files to the stable format. Use 
- &lt;title_reference&gt;qmgmt task create CONVERT_FILES&lt;/title_reference&gt;
- qmgmt task create CONVERT_FILES
- . It is critical that clients running versions older than 4.3 are permanently retired from the cluster before starting this conversion.
- We are consolidating packages for RHEL, Rocky Linux, CentOS Stream, and compatible distributions (like AlmaLinux) into a single, unified repository using the new identifier RH_9 (and corresponding major versions). While old repository paths remain active to ensure a smooth upgrade process, existing installations must update their repository configuration files to use the new RH_9 path for all future package updates. This simplifies maintenance and ensures all compatible RHEL-based systems receive the same packages. See 
- &lt;reference refuri="https://support.quobyte.com/docs/16/latest/installation_packages.html"&gt;https://support.quobyte.com/docs/16/latest/installation_packages.html&lt;/reference&gt;
- https://support.quobyte.com/docs/16/latest/installation_packages.html
-  for how to update the repository configuration.
- You can now attach arbitrary labels to devices (like an inventory ID or a PO number) with "qmgmt label set/get/delete".
- The S3 service now supports Storage classes via Quobyte file lifecycle policies. See S3 Gateway documentation for more information.
- Packages for Debian 13 are now available
- Packages for Linux distributions compatible with Red Hat 10 are now available.
- Added all support for all RHEL-based distributions to install_quobyte
- Add man pages for CLI commands.
- The mount option user_xattr is now set by default for the native Linux client, which enables the namespace 'user' for extended attributes.
- Added JSON output support for qmgmt query files command.
- Fixed crash when accessing the RDMA Queue Pairs status page while RDMA is disabled.
- Fixed a bug that prevented RDMA networking from working if GID index 0 is in use.
- Fixed a bug in the HTTP to HTTPS redirect.
- Fixed a race that could cause clients to see empty volumes or empty volume lists.
- Added a Registry Service status page for the built-in DNS server.
- The built-in DNS server has now better support for multi-home deployments: it is now possible to define a network filter that determines which service IPs are used for HTTP frontend DNS records. If no filter is defined, the records now only contain the IP address of the interface with the default gateway.
- Added alert to warn about hardware errors found in kernel logs.
- Tenant admins are no longer allowed to rename their tenant.
- Fixed a race in Registry Device mounting by FS-UUID.
- Fixed a bug in Azure external location configuration that dropped the shared key from the saved configuration.
- Fixed a problem in analyze volume that led to listing empty files that seem to take space.
- Reduce priority of high-volume metadata maintenance operations to not interfere with production IO.
- Fixed an issued that could cause maintenance tasks to get stuck with long running operations.
- Fixed an issue causing files to have inconsistent file sizes if they were appended to concurrently by multiple clients in a high-load environment.
- Fixed an issue that could cause writes on erasure coded files to fail if data services were restarted in quick succession.
- Resolved an issue where an I/O error or a client process crash could occur if an application called ftruncate to a size of zero on an erasure coded file while a new file snapshot was being created due to the operation.
- No longer aborts when the client was started with 0.0.0.0 as registry address.
- Adapt logging when the metadata cache gets full due to limited system memory.
- Improve qinfo info output for erasure coded files with partial redundancy or files that have not been closed properly.
- Addresses a rare issue where concurrent sequential reads of erasure coded files could occasionally return incorrect data if a storage device briefly went offline.
- Fixed RPCs occasionally failing with a "Connection to ... closed" message while the service is actually reachable.
- Fixed client crash when getxattr is used on certain quobyte-specific attributes on files that don't support them or are moved to an external location.
- NFS: No longer crashed on short remaining lease validity time.
- Increased the frequency of sending whitespace characters for more robust multipart uploads.
- Reduced memory footprint.
- RPC traffic may utilize RDMA.
- The "Create new volume for each bucket" toggle in the S3 Gateway configuration can now be changed without requiring S3 service restart.
- Fixed a bug in the ListObjectsV2 API that caused signature mismatch errors on objects with some special characters.
- Fixed a bug in the CopyObject api that dropped the storage class provided with the request.
- Fixed a bug in the ListObjectVersions API that occasionally resulted in an incorrect NoSuchKey error.
- Improve qinfo retention command line options and error messages.
- Fixed qmgmt to use the currently logged-in Quobyte username for tasks and modified policy comments. Previously, qmgmt used the shell username for these comments.
- Renamed 'qmgmt support' to 'qmgmt support-data-file'.
- Fixed "qmgmt accesskey create" command to output both access key id and secret
- Added --s3-prefix option to files copy command.
- Fixed a bug in copy from S3 task that finished task without copying any files when specifying a prefix.
- Enforce placement and catch-up on-demand maintenance tasks will not interrupt tiering and check files tasks anymore.</changelog>
</package>
<package pkgid="5442e42bcaa95c824f186e9fdfa326534ae3b21bed881f25d760709a680fa693" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="35bc22cb247d6f1e0e4a68f2825395c9b58234890ca687d10fadf043ac89483c" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.6.1" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.1-1" date="1764849600">- Fixed a crash introduced with 4.6 if listxattr was called on the root of a multi volume mount point.
- Fixed a regression in the S3 TLS certificate configuration options.
- Fixed broken qmgmt files command --filters option</changelog>
</package>
<package pkgid="494bfb2907dea07afba2a1ae985a69bbff5f27d0577fed62777102a92fd37d56" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="8d8193a89787fd3df13120bb5c91a25f8fca3bd0ffc48b0573903e459988a1e6" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.6.2" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.6.2-1" date="1766145600">- Packages for Amazon Linux 2023 are now available.
- Fixed an issue with files rejecting operations due to an outdated primary epoch repeatedly after primary failover.
- Fixed a regression introduced with release 4.6 that may have caused writing mismatching block CRCs to files, if they got appended to concurrently by clients on different hosts.
- Fixed 
- &lt;title_reference&gt;qmgmt tenant add_volume_access&lt;/title_reference&gt;
- qmgmt tenant add_volume_access
-  command to set read-only properly.</changelog>
</package>
<package pkgid="e838680250a7ab7d06c8dff888cc4c3d9c746f2614c828a36ca205207fc9ad1a" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="7ac8b544841c91343f6a8ba3242181b96634c773110bbe84fe09cc98324c06fd" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.7" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.7-1" date="1772539200">- Resolved a regression from version 4.6 in the Data Service where concurrent appends from multiple hosts could lead to inconsistent file size reporting. This fix prevents associated Input/Output errors (EIO) during file open operations by ensuring Data Services correctly synchronize file attributes.
- Added support for Oracle S3 to the Data Mover
- The Windows client can be installed with 
- &lt;title_reference&gt;winget install quobyte-client&lt;/title_reference&gt;
- winget install quobyte-client
-  now.
- Added support for Amazon Linux 2023 to the Quobyte installer
- Expanded coverage of device error detection from kernel log.
- Re-enabled support for RSA and SHA1-signed certificates. This restores compatibility for environments affected by recent Java security updates.
- Fixed package dependency issues for SUSE Linux distributions.
- Fixed the installation path for 
- &lt;literal&gt;tuned&lt;/literal&gt;
- tuned
-  profiles on Amazon Linux to ensure they are correctly detected and applied.
- Re-instantiated fallback to deprecated certificate type, which have permissions in certificate subject.
- Fixed Query Engine NOT &lt;property&gt; EXISTS operator.
- Resolved an issue where 
- &lt;literal&gt;umask&lt;/literal&gt;
- umask
-  was incorrectly applied to new directory entries in directories with non-standard ACE permissions.
- Fixed a bug in the Data Mover that caused tasks to fail when copying files from S3.
- Volume policies that match on volume labels are now immediately effective on creation.
- Fixed a client crash that occurred when the Registry service denied a request to list available volumes.
- Resolved a race condition where concurrent writes and truncates from multiple clients on the same file could trigger an 
- &lt;literal&gt;object_was_dropped&lt;/literal&gt;
- object_was_dropped
-  assertion.</changelog>
</package>
<package pkgid="27710ba259fb80534c136425a7a1b6137a6666e52e1b989fb9d8303f5eb55671" name="quobyte-tools" arch="aarch64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
<package pkgid="bad749784ab13ef6f59b5513312ff66a83e1cbd862836413a0bad0ea1ee642e5" name="quobyte-tools" arch="x86_64">
  <version epoch="2" ver="4.8" rel="1"/>
  <changelog author="Quobyte Inc. &lt;support@quobyte.com&gt; - 4.8-1" date="1779278400">- Fixed a bug that prevented signals sent to quobyte-server containers from reaching the actual service process.
- Fixes an issue that prevented the systemd service configs from being reloaded during updates in some setups.
- Fixed a service crash caused by "Access Denied" errors when loading system-wide certificates.
- Extended LDAP Registry logging to include full bind error details. Fixed LDAP bind to ensure a pure authentication request, resolving potential connection resets with sensitive servers.
- Fixed a rare NPE crash bug, that might get triggered by an immediate registry primary failover after election.
- The Health Manager will no longer schedule catch-up tasks for volumes that only have files-with-errors that would be in need for a catch-up.
- Fixed an issue preventing failure domain analysis and alerting from recognizing configuration policies with file scope.
- Fixed iteration for queries with operator directory=/&lt;dirname&gt;.
- Improves volume cleanup tasks to create missing file layouts for empty files, that have been created in an old release around the year of 2018, in order to prevent scheduling of unnecessary enforce placement on-demand tasks.
- Fixed a memory leak in an error path.
- Fixed a bug that prevented recoding files with 0-valued atime or ctime.
- Fixed a minor bug in the DataMover that caused the permissions update of the destination directory while copying from S3.
- Fixed a bug that caused quota usage to spike after recode tasks.
- Fixed DataMover to reject tasks if the source volume does not exist.
- Fixed wrong system directories being used in quobyte-nfs.
- Fixed file metadata cache coherency on Windows with distributed host access.
- Show effective policy rules now also includes rules with file or client scope.
- The qmgmt usage show system command now displays license limits alongside current usage.
- Fixed a bug that caused the qmgmt keystore create-slot and list-system-slots commands to fail.
- Fixed a bug that prevented changing retention timestamp recursively.
- Fixes an issue with the detection of previous installations of Quobyte on SUSE Linux in the installer.
- Fixes an issue that could block install_quobyte on automated package installations with Debian based distros.
- Improves the installers robustness with apt and zypper commands in Debian or SUSE based installations.
- Fixes udevadm missing in quobyte-server container images.
- Fixes an issue where parameters passed to the Quobyte server container images during startup were ignored.</changelog>
</package>
</otherdata>