Repository navigation
Fix/haos zfs sync - #18581
Closed
Thorreke wants to merge 2 commits into
Closed
Fix/haos zfs sync#18581Thorreke wants to merge 2 commits into
Thorreke wants to merge 2 commits into
Conversation
Contributor
Try this branch
bash -c "$(curl -fsSL "https://raw.githubusercontent.com/Thorreke/ProxmoxVE/fix/haos-zfs-sync/vm/haos-vm.sh")"Only the script itself comes from this branch. The engine it loads still |
4 of 11 tasks
Member
|
Thank you for bringing this up, i fixed it in core so it helps all VM scripts: community-scripts/core#223 |
MickLesk
pushed a commit
to community-scripts/core
that referenced
this pull request
Nov 10, 2026
Freshly extracted or converted images leave gigabytes of dirty pages. On a
default ZFS install the image (rpool/var-lib-vz) and the target zvol
(rpool/data) share a pool, so the zvol create inside qm disk import hits
Proxmox's zfs command timeout ("got timeout") while ZFS writes them back.
vm_import_disk now runs a best-effort sync -f on the image first, which
covers every VM script at once instead of patching them one by one.
Refs community-scripts/ProxmoxVE#18580, community-scripts/ProxmoxVE#18581
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✍️ Description
The Home Assistant OS VM installer encounters a reproducible ZFS volume creation timeout when importing the extracted QCOW2 image into local-zfs.
The ZFS volume is created despite the timeout, but the image is not imported.
Testing indicates that the issue is related to pending filesystem writes following image extraction. Explicitly synchronizing the filesystem before importing the disk resolves the issue.
The behavior has been reproduced on a single Proxmox host.
Adding a synchronization step after image extraction seems to fix the issue.
🔗 Related Issue
Fixes #18580
✅ Prerequisites (x in brackets)
Tested on: pve-manager/9.2.3/d0fde103346cf89a (running kernel: 7.0.6-2-pve)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.🤖 AI Assistance (X in brackets)
AGENTS.mdand.github/agents/pve-script-creator.agent.mdas guidance, and the output has been reviewed and corrected to match those guidelines.