Vitastor 3.0.11 released

A single hotfix:

• Fix missing bitmap read error handling in EC reads from cloned images or from images with snapshots potentially leading to invalid (zero) reads during OSD restarts / PG repeerings

⚠️ Warning - if you’re affected, ideally you should pause client I/O during update

2026-05-09 Continue reading →

Vitastor 3.0.10 released

Important bug fixes (new store):

• Fix OSDs possibly refusing to start with “write metadata failed at offset xxx: Invalid argument” (fix buffer alignment during initial garbage collection)
• Rollback change from 3.0.4 - on-disk garbage entries are not skipped on start again. This change doesn’t have any impact normally, but OSDs originally running 3.0.0-3.0.2 and then upgraded to 3.0.9 may hit a bug where 3.0.9 refuses to start due to entries marked as garbage too early and flushed to disk in 3.0.0-3.0.2.

Other changes:

• Auto-select the only RDMA device/port if there is only one
• Rollback one 3.0.9 change - there was no actual use-after-free :) (the problem was only relevant to an unstable development version)
• Fix vitastor-nfs --trace option
• Fix an unintended 1 second sleep in vitastor-cli rm-data
• Fix inode statistics not being cleared for a deleted pool
• Fix print to stdout in client

2026-04-27 Continue reading →

Vitastor 3.0.9 released

• Fix clients reading from snapshots incorrectly on retries (for example when OSDs were restarted during read)
• Fix a possible “send-after-free” in OSD. It turned out that this problem was never present in any released versions and the fix was only relevant for an unstable development branch. The change will be rolled back in 3.0.10.
• Fix broken garbage collection in the new store leading to very high memory usage
• Make the new store do full garbage collection on OSD startup by default (can be turned off with a new gc_on_start parameter)
• Make startup logging with the new store more informative, allow to log amount of garbage with log_level > 1
• Fix OSD crashing when handling a read_bitmap operation from a deleted object with the new store

2026-04-04 Continue reading →

Vitastor 3.0.8 released

• Surrogate increment-only peer ID is now used instead of the file descriptor number, and client cleanup sequence is reworked in another attempt to fix a possible PG hang in ‘peering’ states. The history of this bug is unclear and it still hasn’t been reproduced in tests, but several users have reported it since 3.0.4 (only with enabled RDMA).
• Fix a minor bug where an OSD could skip reporting misplaced PG state when moving an object in non-immediate_commit mode.
• Add Ubuntu 26.04 (Resolute Raccoon) support and patches for qemu 10.2 and libvirt 12.0

Note: version 3.0.7 is re-released as 3.0.8 because of an originally incorrect build.

2026-03-29 Continue reading →

Vitastor 3.0.6 released

• Fix one more bug in old store checksums O_o - checksum verification wasn’t working correctly on reads quickly after small initial offsetted writes (when a BIG_WRITE was read from the journal). Could lead to incorrect detection of objects as corrupted.
• Fix clients possibly not destroyed after being switched to RDMA. Not 100% verified, but in theory it could rarely lead to PGs hanging in peering/stopping states with RDMA enabled.
• Use vitastor-cli in the Cinder driver for modifications instead of direct etcd interaction.
• Fix mon_https_ca parsing.
• Fix Docker install.sh script, add instructions for Podman.

2026-03-22 Continue reading →