Vitastor 2.1.0 released

Separate cluster network support, RDMA-CM and allow_net_split setting.

2025-04-01 Continue reading →

First release of Vitastor S3

The moment has come - Vitastor S3 implementation based on Zenko CloudServer is finally released.

Key differences from the prototype:

• Volume defragmentation is implemented;
• Volume metadata may now be stored in the same MongoDB as object metadata, not just in VitastorKV;
• Tests for the Vitastor S3 backend added;
• S3 is now packaged in a convenient Docker build.

2025-03-16 Continue reading →

Vitastor 2.0.0 released

No breaking features, it’s 2.0.0 just because it includes S3 and because there are already too many 1.x releases :).

2025-03-16 Continue reading →

Vitastor 1.11.0 released

New features

• Support containerized Vitastor installations: http://vitastor.io/en/docs/installation/docker.html
• Add new functions to the node.js binding: delete(), get_immediate_commit(), on_ready(), get_min_io_size(), get_max_atomic_write_size()
• S3 (Zenko Cloudserver with Vitastor support) is coming shortly and will be released separately

2025-03-01 Continue reading →

Vitastor 1.10.1 released

New features

• Add “deleted” image flag which is set when vitastor-cli rm starts to delete an image, but can’t delete it fully due to inactive PGs or stopped OSDs
• Support JSON output in vitastor-disk prepare and purge
• Show backfillfull pools in vitastor-cli status
• Make object listings consistent (used in vitastor-cli rm/rm-data/merge/etc). This means that there is now a guarantee that if a data block is present when you invoke rm, rm will attempt to delete it, even if rm is invoked when the PG switches state. Previously in such cases rm could skip and leave some objects behind as garbage, and merge probably could incorrectly move data between snapshots.
• Make deletions (rm/rm-data) consistent. This means that rm/rm-data will either complete successfully and delete all requested image data or complete with an error if some objects could not be deleted or if there is a possibility that some data is left on stopped OSDs. Previously, when some PGs or OSDs were inactive at the moment of deletion, rm-data was behaving incorrectly: it wasn’t retrying deletions failed due to dropped OSD connections, it could hang waiting for PGs to activate, and it could return with a successful error code while some garbage was still possibly left on some OSDs. Deletions are not fully atomic cluster-wide yet, which means that you still have to repeat the deletion request after you return stopped OSDs back, but now you always know for sure if you have to repeat it.

2025-01-03 Continue reading →

Vitastor 1.10.0 released

VitastorFS in CSI, NFS-RDMA, backfillfull and more.

2024-12-19 Continue reading →

Vitastor 1.9.3 released

• Support custom hybrid OSD creation (vitastor-disk prepare --hybrid --fast-devices /dev/xxx,/dev/yyy)
• Auto-change partition paths to /dev/disk/by-partuuid/ in vitastor-disk prepare
• Allow to select cached I/O in vitastor-disk commands
• Fix multiple bugs in vitastor-disk resize & add tests for them
• Fix vitastor-disk write-meta/write-journal in superblock-based mode writing it to an incorrect device
• Fix vitastor-disk prepare sometimes again not seeing new partitions
• Cleanup PG history and stats of deleted pools
• Fix “is already mounted” checks in CSI

2024-11-07 Continue reading →

Vitastor 1.9.2 released

New features

• Support resizing normal vitastor-disk partitions and moving journal/metadata: vitastor-disk resize
• Support simple forms of vitastor-disk {dump,write}-{meta,journal} for OSD partitions

2024-10-20 Continue reading →

Vitastor 1.9.1 released

Hotfixes for OpenNebula and upgrade hotfix for 1.7

• Fix deploy.vitastor, save.vitastor, restore.vitastor scripts not working for nodes other than master oned
• Fix deploy.vitastor not working for VMs without Vitastor disks
• Disable clearing old PG configuration when upgrading from 1.7 or older versions (it was breaking old clients)

2024-09-14 Continue reading →

Vitastor 1.9.0 released

• OpenNebula support! Installation instructions
• Added vitastor-cli rm --exact|–matching command
• Added vitastor-cli dd command - copy files between Vitastor images, files and pipes
• Add a startup timeout to vitastor-cli to not wait for etcd infinitely
• Fix non-working OSD_OP_READ_CHAIN_BITMAP O_o
• Autodetect block_size/bitmap_granularity/immediate_commit when creating pools
• Do not allow to create multiple pools with the same name from vitastor-cli
• Fix skip_cache_check option not applied due to type issue (see github issue #70)

2024-09-06 Continue reading →