Latest Posts

Vitastor 3.0.1 released

Important fixes

  • Disable RWF_ATOMIC by default because Linux incorrectly requires all atomic writes to be power-of-2-sized and length-aligned. Details: use_atomic_flag
  • Fix cross-pool snapshots not working at all - always reading old data after taking the snapshot
  • Fix level_placement (broken in 2.2.0)
  • Fix CAS write return values in the client library (broken in 2.4.4, also breaking unaligned writes in VitastorFS)
  • Fix VitastorFS possibly losing some of intersecting parallel unaligned writes
  • Prevent possible reads of the old data during unfinished intent writes in the new store
  • Tests added for all of above problems to prevent future regressions

2025-12-22 Continue reading →

Vitastor 3.0.0 released

A single new feature: the new log-structured metadata store implementation, described in the presentation from Moscow Highload’2025 (check it out here).

It’s now the default store for new OSDs. The support for the old store is also left in place, you can still choose it for new OSDs with vitastor-disk prepare --meta_format 2.

OSDs from previous versions with the old store format will also continue to operate just like before.

Some documentation: atomic_write_size, meta_format.

2025-12-06 Continue reading →

Vitastor 2.4.4 released

  • Implement vitastor-kv rescue command which dumps all readable blocks from the database regardless of the tree structure and allows to recover a corrupted database.
  • Simplify primary OSD selection - use just PG number instead of the hash. This allows to distribute primary OSDs more evenly and reach better read speeds.
  • Fix vitastor-kv-stress hang on parallel list & reopen.
  • Fix CAS writes without immediate_commit. Fix is sufficient for vitastor-kv to operate correctly in non-immediate_commit pools.
  • Fix NFS ACCESS calls for broken inodes (allow root access to them).
  • Fix broken vitastor-kv-stress --runtime parameter.
  • Fix bad vitastor-kv dump output buffering leading to incorrect JSON in dumps.
  • Fix writing garbage from uninitialized memory to the empty space in VitastorKV DB.
  • Refactor some code in preparation to the release of the new log-structured metadata store.
  • Replace assert(done != expected) error message, probably caused by kernel issues with zero-copy TCP send, with a more concise error description.

2025-12-01 Continue reading →

Vitastor 2.4.3 released

  • Daemonize before forking in NFS proxy to fix OSD RDMA support (#107)
  • Fix possible PG_INCOMPLETE on node outage when allow_net_split is false
  • Fix build under Ubuntu 25.10
  • Fix journal_no_same_sector_overwrites mode after optimizing WA (#109)

2025-11-09 Continue reading →

Vitastor 2.4.2 released

  • Fix make-etcd broken after adding ipv6 support in 2.4.1 :)
  • Do not mark “inverse child” as deleted during rename-delete
  • Support QEMU 10.1

2025-11-04 Continue reading →

Vitastor 2.4.1 released

  • Optimize WA - reduce it from 4-5 to 3.x by batching journal writes
  • Fix ls-pool showing wrong used % when osds are reweighted (#105)
  • Fix vitastor-cli rm sometimes hanging when PGs are down (#99)
  • Fix vitastor-cli ls displaying raw used space for all inodes when -p is specified (#101)
  • Fix “Cannot set property of undefined” in monitor when deleting pool with live inode op stats (#103)
  • Revert vitastor-kv change from 2.2.0 leading to crashes in vitastor-kv-stress (#100)
  • Add pg_size change check for XOR pools
  • Fix root access to VitastorFS files
  • Add IPv6 support to make-etcd
  • Fix IPv6 etcd address support in OSD & client library

2025-10-29 Continue reading →

Vitastor 2.4.0 released

New features

  • Support UBLK in CSI and make it the default
  • Add image tree output: vitastor-cli ls --tree
  • Add vitastor-disk prepare --dry-run option

2025-09-24 Continue reading →

Vitastor 2.3.0 released

ublk, Veeam and checksum enablement fix.

2025-08-25 Continue reading →

Vitastor 2.2.3 released

Bugfix release.

2025-07-30 Continue reading →

Vitastor 2.2.2 released

  • Fix a bug introduced in 2.2.0 - pg_locks weren’t disabled for pools without local_reads correctly which could lead to inactive pools during various operations
  • Fix an old bug where OSDs could send sub-operations to incorrect peer OSDs when their connections were stopped and reestablished quickly, in 2.2.0 it was usually leading to “sequencing broken” messages in OSD logs
  • Fix debug use_sync_send_recv mode

2025-06-07 Continue reading →

Older Posts →