Based on the information provided we know that the VM configuration does not have a reference to any snapshots. However, the snapshots exits on the backend. They had to be created by an operator via PVE at some point. How the reference got lost...
Can you provide additional information:
pveversion
qm config [vmid]
cat /etc/pve/storage.cfg
cat /etc/pve/qemu-server/[vmid].conf
pvesm status
Are other VMs running on the same node? Are they located on the same storage (qm config [vmid])
Has...
The action you took is specific to snapshot, the error message is specific to snapshot, so we can be reasonably certain that the problem is related to snapshot management. However, it is likely not related to the origin of the VM. The fact that a...
The migration path is not relevant. You should examine the current state of the LVM as suggested previously. Post the results here as text output encoded with CODE tags.
The two primary outcomes are: the snapshot exists on disk and does not exist...
You should start by checking your LVM structure:
lvs
lvdisplay
etc
I am not sure how you got into this state, backtracking your steps may be a good idea. If there is an edge case of snapshots being orphaned, I am sure developers would like to...
Hi @ogrimia , welcome to the forum.
You raised some strong points, and several of them certainly have merit. From what you’ve written, it sounds like you have the skills to make a real impact - why not consider applying for a position...
Ah - as I planned tonight - I intercepted the API call, converted it into a cURL command and that worked fine after a bit of tweaking.
Maybe not the official way, but it works for me
This may be helpful:
https://forum.proxmox.com/threads/clean-shutdown-of-whole-cluster.121116/#post-526462
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
You should be able to unmap a particular LUN from the target without affecting other LUNs.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I don't think this thread is about the session timeout. It's the fact that PVE uses SMB connect/teardown as a means to probe/healthcheck the CIFS storage.
https://github.com/proxmox/pve-storage/blob/master/src/PVE/Storage/CIFSPlugin.pm#L271...
Hi @macmino,
There are a few possible approaches here:
Enable/disable the storage as needed. If it’s strictly used for backups, this might be sufficient, though I haven’t personally tested it (see man pvesm).
Follow the workaround mentioned in...
Makes sense. In that case you can use LACP on storage and host side.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @markeczzz .
Yes, you can use the same hardware with PVE. It should be very stable, assuming there’s nothing unusual in your specific infrastructure. The best practices are essentially the same as with any FC-based setup: dual HBAs, dual...
Hi @tmerrill , welcome to the forum.
This is the key to your question. Does the above mean that switches are not MLAG connected?
A single VLAN that spans two isolated switches?
You can take a look at this article...
Hi @JonesHerbet, welcome to the forum.
Since you’re looking to refresh your infrastructure, it’s worth taking a step back and considering a more comprehensive update. Replacing HDDs with NVMe is a good start. You should also review your network...
Sounds like something that would be perpetuated by a storage vendor who couldn't figure out how to build a good iSCSI stack and/or support an LACP bond :-)
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
If this was my environment, I were limited in number of NICs that could be added to the host, and I was not looking to create a one-of-the-kind config, I would:
- MLAG the network switches
- configure LACP across the switches (either with MTU...
The storage content required for Containers is "rootdir". Not all supported storage pool types support all content types. For example, raw iSCSI storage (Block) does not support Snippets or ISO. The built-in iSCSI type also does not support...
You have an L2/L3/L4 issue, not L7. If nothing else changes - it will not make a difference whether you use NFS or iSCSI.
Were you also running a hypervisor and placing the VMs on this host at the same time?
Blockbridge : Ultra low latency...