mirrors/talos-extensions
1
0
Fork 0
mirror of https://github.com/siderolabs/extensions.git synced 2026-05-05 04:06:38 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: update zfs readme for existing pools

Browse Source 
Adds documentation for troubleshooting existing pools

Co-authored-by: Dmitrii Sharshakov <d3dx12.xx@gmail.com>
Signed-off-by: Maximilien McDermott <mcder018@live.com>
Signed-off-by: Noel Georgi <git@frezbo.dev>
This commit is contained in:
veymax 2025-09-02 20:04:14 -05:00 committed by Noel Georgi
parent b86a64b230
commit caa10a495f
No known key found for this signature in database
GPG Key ID: 21A9F444075C9E36
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
storage/zfs/README.md
View File

@ -122,3 +122,22 @@ talosctl mounts | grep <mount of zfs raid you specified (/var/...)>
```
You should see the mount.
## Use existing pools
If you have existing pools, they will be automatically detected and used.
However, you may need to enter a debug shell and modify the pool configuration in order for them to work with Talos.
Turn off Samba and NFS share settings.
In addition, some SELinux pool policies are currently incompatible with Talos. If you see errors like this:
```bash
node_name: kern: warning: [2025-09-03T00:34:28.924235026Z]: SELinux: Unable to set superblock options before the security server is initialized
```
You can resolve this by modifying the ZFS pool settings to disable SELinux on the volume:
```bash
kubectl -n kube-system debug -it --profile sysadmin --image=alpine node/<node name>
chroot /host zfs set context=none fscontext=none defcontext=none rootcontext=none pool_name
chroot /host zfs set context=none fscontext=none defcontext=none rootcontext=none pool_name/child_dataset_name
# Review the settings to make sure they were changed correctly
chroot /host zfs get all
```