Skip to content

zark 2.3.3

Latest

Choose a tag to compare

@github-actions github-actions released this 18 Nov 20:49
· 3 commits to main since this release
v2.3.3
c37a04e

zark 2.3.3 is a small fix release after 2.3.2: the command line's positional arguments, the read-backs of backup and fullcheck, recover's restore table, the package's Recommends, and the docs on running zark from a live session. It supports Ubuntu 24.04 LTS, 26.04 LTS and 26.10, and is published in the PPA for the three series.

What's changed

  • Every command refuses a positional argument it does not take, before anything runs: zark <command>: unexpected argument <arg>, exit status 2, as 2.3.2 refuses an unknown option. Until now most commands ignored it: zark backup foo ran a backup.
  • The package recommends attr: the self-test's BOOT-03 check needs setfattr and getfattr, which an Ubuntu live session does not have.

What's fixed

  • backup's and fullcheck's read-backs accept only the pool that was written: another pool of the same name at the drive's device is not read back as the drive. backup says BACKUP NOT VERIFIED; fullcheck records the check as not finished, and keeps any damage its scrub found. A GUID that cannot be read at the read-back is said as such, not as another pool.
  • recover's restore table keeps its columns when a dataset name or a snapshot label is longer than 44 characters.
  • Running zark from a live session: keep the release tarball on the USB stick and extract it into /tmp, which is in memory there. Extracted on a FAT stick, its files have no execute bit and ./zark does not run. README, the manual page and the package's description now say so, and the quick start gives prepare its device.

The full list is in CHANGELOG.md.

Upgrading from 2.3.2

sudo apt upgrade. No sudo zark setup is needed: the guards do not change. apt installs attr with it unless Recommends are turned off. A script or timer that passes a command a word it does not take now stops with exit status 2. Nothing on a drive or in /etc/zark changes; 2.3.2 reads everything 2.3.3 writes. Details in docs/UPGRADING.md.

Known limitations

Those of 2.3.2 still hold, among them OpenZFS #18394 on a zpool clear after a drive goes away, which zark never runs itself. New in this list: mount, umount and simulate ignore a word they do not know where they take one, and zark does not check whether a drive is a zoned block device (SMR, ZNS). See the CHANGELOG.

Install

sudo add-apt-repository ppa:juanmitaboada/zark
sudo apt update
sudo apt install zark

For recovery from a live session, keep zark_2.3.3.tar.gz below on a USB stick, then in the live session:

tar xzf <the stick's folder>/zark_2.3.3.tar.gz -C /tmp
cd /tmp/zark
sudo ./zark recover

zark_2.3.3-1_amd64.deb is for machines without the PPA: it is built from the same source as the PPA's packages and versioned 2.3.3-1. The PPA's carry a series suffix and sort below it, so on a machine with the PPA, install with apt.