Vitastor 3.0.4 released

New store bug fixes

• Fix very slow OSD startup (hours) possible in unlucky cases
• Fix incorrect garbage entry validation on start in some cases, preventing OSD startup
• Fix small_write_throttling not functioning and either hanging or crashing OSDs
• Fix “different fact_versions returned from subops” error possible with EC in some cases
• Add a recovery option for the new store: skip_corrupted_meta_entries
• Disable intent writes (even 4k) for hybrid OSDs by default for better write buffering

2026-03-03 Continue reading →

Vitastor 3.0.3 released

• Fix csum_block_size > 0 unusable with atomic writes in the new store (almost all atomic write requests generated invalid checksums with csum_block_size > 0)
• Fix monitor sometimes randomly failing to optimize PGs with the “problem is infeasible or unbounded” message due to not waiting to read full stdout of lp_solve
• Remove reshard_abort optimisation to fix chunked resharding introduced in 3.0.2 possibly corrupting in-memory OSD state when handling multiple rapid PG count change requests
• Fix removed inodes not disappearing from OSD statistics in the new store, leading to bloating of the statistics with old inodes
• Increase test coverage for the new store and fix several minor bugs:
  • Enabling/disabling of used_for_app was recalculating inode space statistics incorrectly
  • Fix object metadata validation on OSD startup rejecting some correct sequences of entries, possibly leading to OSD being unable to start
  • Fix PG activation with EC failing in rare cases with EBUSY when requesting to commit an already committed write
  • Fix a theoretically possible metadata writeback issue on ENOSPC during commit
• Fix monitor failing to optimize PGs in presence of a host with name convertible to js Number (like 04e278988710) :D
• Fix vitastor-cli dd sometimes (rarely) truncating the image when writing to stdout
• Fix a theoretically possible client connection object leak when io_uring is full
• Fix a leak of RDMA-CM connection objects
• Fix crashes with data_block_size < 32KB (useless setup, but anyway) (#113)

2026-02-08 Continue reading →

Vitastor 3.0.2 released

• Antietcd is now officially safe to use: the release includes a fixed version of antietcd which passes Jepsen transaction serializability tests.
• Fix a huge checksum bug in the old store: incorrect checksums for small initial writes. The bug affected writes of exactly csum_block_size (4k by default) into new (unallocated) objects and generated invalid checksums in the store for the written 4k block. Moreover, generation of these invalid checksums was very slow because it was calculating CRC32 for 4 GB of zeroes. If the block wasn’t then overwritten as a part of a larger write request it became unreadable even though the stored data was correct. The bug affected all versions since 1.0.0, or since 2.3.0 because vitastor-disk didn’t allow to enable checksums prior to 2.3.0 because of another bug. O:-)
• Prevent OSD disconnections due to long blocking of event-loop caused by PG resharding (moving objects between old and new PGs in memory) when changing pool PG count or just on restart of an OSD with a large database (for example, with a filled 8 TB SSD). The issue should now be fixed because OSD now performs resharding in chunks with pauses between chunks.
• Prevent pools stuck in paused state on an aborted PG count change.
• Fix a possible OSD crash with “division by zero” when trying to handle an operation before pool PG count is applied to the in-memory store.

2026-01-25 Continue reading →

Small, but with transaction isolation: writing Jepsen tests for Antietcd

Since version 1.7.0, Vitastor has a built-in etcd replacement — Antietcd.

It’s implemented in Node.js and is very simple — it has just a couple thousand lines of code. It doesn’t implement all features of etcd, but it’s absolutely sufficient for a fully functional Vitastor cluster — all the essential features are present, and in some ways, it’s even better than etcd — for example, Antietcd allows to avoid storing “temporary” data on disk.

However, until recently, there was no answer to the question: can it really be used in production? Does it work correctly?

Below is the story of the search for an answer. A story with a happy ending :)

2026-01-22 Continue reading →

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 →