You likely selected Move instead of Clone.
ah, so that wasnât so clear. So if I clone it, then the hidden .ix-virt volume becomes the active volume and the existing HAOS zvol replicates and serves as a backup?
So, this is something that has changed between RC and the release.
I donât understand why we now have to clone or move the zvol to use it. I already have it set up in the location I want it to be. Why canât we just select and use the zvol as before? Obviously, I donât understand why this change was required. Can someone please explain?
Does this get rid of the extra root drive that is being created? Or is the clone going to the root drive instead of having an empty root and a zvol attached?
It didnât work like this in the RC - I have (well I had) a similar setup. I donât understand why we canât just set up our NAS with stuff where we want it to be. Why does stuff need to be manipulated and moved around? Is it really that hard to let us manage our own data locations. I was looking forward to eventually moving my primary HAOS back to TrueNAS, but not so much anymore.
My understanding of this, and Iâm not a developer so that is second-hand, is that there were some significant performance issues with mounted zvols discovered in the early release versions, so that is part of the motivation. The other purpose, which is indicated in the UI help text, is to allow Incus to fully manage the instance volumes, which in turn exposes them for Incusâs native backup/restore and snapshot functionality.
Work is in progress to expose these features in the UI.
Currently it does not, but I believe there is also development work in progress to allow you to select a volume and then make it the root disk or move it to the root disk at least, so an additional volume mount will not be needed.
Thank you for the explanation.
When I update this guide, do you think it would be better to suggest a clone or move when importing the zvol?
My guess would be clone is more useful for people trying it out, since that allows for easier roll back to the 24.10 boot environment if needed.