failed to register layer: exit status 2: "/sbin/zfs zfs snapshot pond/docker/4522c1adffaf266062442dba2eb347084d774267a124d1bd7a04e6b3cb9634f0@371563767" => cannot open 'pond/docker/4522c1adffaf266062442dba2eb347084d774267a124d1bd7a04e6b3cb9634f0': dataset does not exist usage: sn...
Doing a strings.Contains of "dataset does not exist" in err - How to verify it - Description for the changelog Ignores "dataset does not exist" error when removing dataset on ZFS (#43080) name:=d.zfsPath(id) dataset:=zfs.Dataset{Name:name} err:=dataset.Destroy(zfs.DestroyRecursive) if...
When compression is enabled on a dataset, ZFS tries to compress allnewblocks before writing them and decompresses them on reading. Already existing data will not be compressed retroactively. You can enable compression with: # zfs set compression=<algorithm> <dataset> ...
A dataset cannot be destroyed if snapshots of the dataset exist. For example:# zfs destroy tank/home/ahrens cannot destroy 'tank/home/ahrens': filesystem has children use '-r' to destroy the following datasets: tank/home/ahrens@tuesday tank/home/ahrens@wednesday tank/home/ahrens@thursday...
Therefquotaproperty limits the amount of space a dataset can consume. This property enforces a hard limit on the amount of space that can be used. This hard limit does not include space used by descendents, such as snapshots and clones. ...
Include the dataset’s properties in the stream. This flag is implicit when -R is specified. The receiving system must also support this feature. -n Do a dry-run ("No-op") send. Do not generate any actual send data. This is useful in conjunction with the -v or -P flags to determi...
prevent automounting per dataset (values are on, off, noauto) If you need e.g. boot to fail hard on a missing ZFS pool, consider zfs set mountpoint=legacy poolname/fsname Then you can use an fstab entry like: poolname/fsname /export/media zfs defaults 0 0 performance tweaking...
Condition: SE Linuxonorpermissive xattr=on for ZFS dataset Workaround: Umount & mount the said dataset should release the space A fix that people warn against, quoting possible data loss: # zfs set xattr=sa YourDataSet Discussion on GitHub....
Record size sets the suggested block size for a volume in a ZFS dataset. Choose whether to use the default record size of 128 KiB, or to set a custom record size for the volume. We recommend using the default setting for the majority of use cases. For more information about the record...
Optimize OpenZFS snapshots. Learn which data benefits from snapshots, how long to keep them, and how to avoid performance bottlenecks.