gian/incus-mirror
1
0
Fork 0
mirror of https://github.com/lxc/incus synced 2026-08-02 05:26:46 +00:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

docs: Clarify the sentence about Incus owning the ZFS pool/dataset

Browse Source 
Signed-off-by: Lucas Desgouilles <ldesgoui@gmail.com>
This commit is contained in:
Lucas Desgouilles 2026-07-31 17:28:40 +02:00 committed by ldesgoui
parent 90429bf42f
commit 28c287796f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/reference/storage_zfs.md
View File

@ -29,8 +29,8 @@ These {spellexception}`datasets` can be of different types:
The `zfs` driver in Incus uses {spellexception}`ZFS filesystems` and ZFS volumes for images and custom storage volumes, and ZFS snapshots and clones to create instances from images and for instance and custom volume snapshots.
By default, Incus enables compression when creating a ZFS pool.
Incus assumes that it has full control over the ZFS pool and {spellexception}`dataset`.
Therefore, you should never maintain any {spellexception}`datasets` or file system entities that are not owned by Incus in a ZFS pool or {spellexception}`dataset`, because Incus might delete them.
Incus assumes that it has full control over what you gave it when creating the storage pool, be it a ZFS pool or a {spellexception}`dataset`.
Therefore, you should never try to maintain any children {spellexception}`datasets` or file system entities, because Incus might delete them.
Due to the way copy-on-write works in ZFS, parent {spellexception}`ZFS filesystems` can't be removed until all children are gone.
As a result, Incus automatically renames any objects that are removed but still referenced.