Data on ZFS Dataset Mysteriously Gone: Check Mountpoints Before You Panic
Data on ZFS dataset mysteriously gone? It's usually a mountpoint or bind mount issue, not actual loss. Here's the diagnostic order that finds it.
Homelab & Vietnam
184 posts
Data on ZFS dataset mysteriously gone? It's usually a mountpoint or bind mount issue, not actual loss. Here's the diagnostic order that finds it.
Mouse offset in SPICE is a pointer mode mismatch. Enable tablet mode, install spice-vdagent, and check scaling to fix it for good.
Proxmox cloud-init drive shows as cdrom by design. Here's how to tell the expected cloud-init CD-ROM from a real bus or storage remap.
A Proxmox hookscript fails when it tries to do too much at once. The phase argument, locked VM config, and root's environment all change what works.
Proxmox kernel not updating? It's usually apt pinning or a missing meta-package. Here's how to check both and get the new kernel installed.
A SUSPENDED ZFS pool blocks all I/O, so zpool clear and scrub won't work until you offline the problem disk. Here's the order that actually recovers it.
The Proxmox API endpoint /access/permissions doesn't expand pool ACLs the way you'd think. Here's exactly what it returns for pool-scoped roles and how to
Proxmox iSCSI traffic goes over the management network because open-iscsi binds by destination IP.
Those audit: PROCTITLE proctitle="ebtables-restore" lines come from pve-firewall reloading rules. Filter them with an audit rule, not by disabling auditd.
Proxmox ZFS storage summary shows Size, Used, and Avail from zpool list, but the per-dataset numbers come from zfs list. Here's the mapping.