I currently have an issue where I cannot import custom ISOs, because there is ‘no storage left on device’.
manager@IncusManageVM:~$ incus storage volume import mainpool-vmdata cisco_files/CatalystCenter/CatC-SW-2.3.7.9-VA.iso CatC-SW-2.3.7.9-VA.iso --type=iso
Importing custom volume: 49% (228.15MB/s)Error: write /var/lib/incus/isos/incus_iso_2319347180: no space left on device
mainpool-vmdata has more then enough storage and actually the local zfs pool should have as well, although I know that in the background IncusOS creates a root partition that’s much smaller than that (I think around 30GB).
Is the a way to change where the ISOs are stored when uploading them before they are imported as volumes to the specified pool?
I could not find anything regarding this in the docs. Only thing I found was about changing the storage location for images, logs, backups:
incus config set storage.images_volume mainpool-vmdata/images
incus config set storage.backups_volume mainpool-vmdata/backups
incus config set storage.logs_volume mainpool-vmdata/logs
Can someone point me in the right direction? Maybe I missed something in the docs? I’m quite new to Incus / IncusOS.
Hmm, that strikes me as something that shouldn’t even need to hit temporary storage so long as we know the full size of it during the transfer… We already know what pool it’s headed for and it will be stored exactly as it is.
Can you file an issue at Sign in to GitHub · GitHub so we can look at having imported ISOs go directly to the storage pool.
And yeah, at minimum we should use images/ as the temporary storage (bit of a hack) as that can at least be offloaded to a volume on the pool instead of writing to the root disk.
So this means that currently there is no way of importing ISO files bigger than 30GB on IncusOS? Since you can’t really mount /var/lib/incus/isos to another mountpoint/storage pool. Or is there some way around it?
Correct. On the upside, it should be very easy to at least move the temporary file to the images volume and hopefully not too hard to allow streaming the data. So Incus 7.0 (end of April) should have a fix for this, if we don’t cherry-pick something even sooner.
