Search results

i have explicitly set "format qcow2" for the datastore because i want nothing but qcow2 on that - but the disk is still raw after "qm disk move..." so i wonder, what's the purpose of this param or where does it apply (and where not) i guess my expectation is wrong that it applies to "qm disk...

hello, there is some format param described at https://pve.proxmox.com/wiki/Storage format Default image format (raw|qcow2|vmdk) which also can be set with command pvesm set <SR> --format <format> which storage actions should this format param apply to, when being set ? i would expect that...

i have made a proof of concept and i could successfully use a file as a virtual usb stick via dummy_hcd/g_g_mass_storage kernel modules https://bugzilla.proxmox.com/show_bug.cgi?id=4879

i have made a proof of concept and i could successfully use a file as a virtual usb stick via dummy_hcd/g_g_mass_storage kernel modules https://bugzilla.proxmox.com/show_bug.cgi?id=4879

what zfs version do your truenas have?

>I have a single VM (OPNsense) that is writing around 70k per minute (showing in VM summary tab) which is less than 5MB / hour. what do you measure inside the VM ?

there is a terraform discord chat, i guess you get better help/support there https://www.reddit.com/r/Terraform/comments/iktkzm/discordslack/

führ das mal auf der konsole aus, da siehst du mehr

linking to bugzilla ticket https://bugzilla.proxmox.com/show_bug.cgi?id=4835

hier gibt es ein bugzilla ticket dazu. https://bugzilla.proxmox.com/show_bug.cgi?id=4835 aktuell leider geschlossen "works for me". wenn es keine gegensprache oder reaktion gibt werd ich das die tage versuchen wieder öffnen. oder vielleicht öffnet jemand anderes es nochmal. @TosH45 @Wintendo

thank you

see subject of this post

can you disable nfs mounts to make the errors below go away, to make sure it's not the nfs mounts causing this problem? there is some ticket and linked threads on the failing of zfs-import systemd service at https://bugzilla.proxmox.com/show_bug.cgi?id=4835 , these appear to be non critical or...

could you exactly point to the line in the logfile where you were dropping to the emergency shell / initramfs? what message do you see there?

i have also come across this issue today - fresh install of pve 8.1 inside a VM - zfs rootfs (rpool) - added a single disk and put zfs on that via pve gui (name testzfs) - reboot getting several of these on reboot Feb 13 21:48:27 pve systemd[1]: Starting zfs-import-cache.service - Import ZFS...

now, that's really really weird Feb 13 14:28:52 proxmox zpool[1275]: cannot import 'rpool': a pool with that name already exists Feb 13 14:28:52 proxmox zpool[1275]: use the form 'zpool import <pool | id> <newpool>' to give it a new name Feb 13 14:28:52 proxmox systemd[1]...

i'm curious how the problem can continue to exist ,when you have set volmode=dev on zd48 and zd96 (corresponding) zvols , as zpool import won't find any pool then i assume that you probably did not set volmode=dev on both !?

i just wanted to write that a typical problem with zfs boot problems is name clash with existing pool names. i had that some times when attaching old root disk via usb and the system then could not decide which rpool to import and apparently, that's your problem: Feb 12 15:09:53 proxmox...

> Of course I can ;-) Which GPT bootsector we're talking about? The one of the PVE host, or the one of the Solaris VM? the solaris VM one

i have searched a little bit in kernel code. whith my limited knowledge, it appears to me that there is no way to disable gpt scanning on blockdevices. i wonder that we can disable partition scan/device node creation. maybe missing feature in linux kernel !?