Vitastor 1.11.0 released

2025-03-01

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

Bug fixes

  • Use IP-derived etcd node names in make-etcd
  • Set short name of the OSD process to display in top
  • Fix snap-create without pool_id failing when there are multiple pools
  • Several bugs are fixed in the write-back cache, it should now be stable:
    • Fix incorrect snapshot reads from dirty write-back cache
    • Do not try to repeat pending writebacks on OSD reconnections
    • Fix client hangs with multiple SYNCs in the writeback queue
    • Fix client hangs do to incorrect calculation of the writeback queue size
  • Several improvements for NBD mapping/unmapping:
    • Add a workaround for race condition in the Linux kernel NBD driver leading to vitastor-nbd sometimes breaking a previously mapped device instead of setting up a new one
    • Check if the device is actually mapped in vitastor-nbd unmap
    • Fix device name/number validation in vitastor-nbd
  • Fix OSD crashes after starting with corrupted metadata - from now it will skip corrupted metadata entries and heal itself
  • Fix scrubbing of misplaced objects and object state recalculation after vitastor-cli fix - previously, an OSD restart could be required to fix object states
  • Make primary OSD distribution more stable by using murmur3 hash instead of the old pseudo-rng
  • Fix monitor sometimes racing with itself - do not touch /pool/stats from stats aggregation if PG recheck is active
  • Sort vitastor-cli ls output by name by default
  • Update antietcd to 1.1.2