One option is to find the Task that contains the execution time.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @Biggin747 , you'd need to provide actual system state for a meaningful analysis:
# 1. See the pool and what's in it
pvesh get /pools/<poolname> --output-format json
# 2. See ALL ACLs in the cluster
pveum acl list
# 3. Check the custom...
All achievable depending on the many other variables in the infrastructure.
Understood, I was confused by this statement:
It is a bit hard to get a full picture from the bits and pieces you provided over several messages. Especially given...
How did you come to this particular conclusion? Perhaps you can share your migration settings, how its executed, and what errors you received?
I would disagree with this statement.
Generally, this is a recommended way - VMware strongly...
Hi @wendellrodriguez , its best to open your own thread vs "hijacking" a loosely related thread of another poster.
The short answer to your question - yes, it should be possible. Thousands of people have done similar migrations. Have you tried...
If this was my environment and something I wanted to resolve, I would even try:
Creating a new storage pool, manually add disks to this pull (pvesm alloc) and test the response time until it exceeds reasonable time. Reduce the number of disks -...
Next steps are:
Execute pvesm list <storage>.
Examine your browser's developer tools to see whether a particular API call is hanging or taking an unusually long time.
Use pvesh to execute the relevant storage listing calls and determine where...
Few notes:
- Please use </> CODE tags from the post box menu when pasting text/config/etc. It makes the information much more readable
- You appear to have multiple paths to your storage, so you will need to configure Multipath for proper...
Hi @kaushal_shah,
There is a wealth of documentation, blog posts, and video material available on configuring PVE. Your question is quite broad, as production environment planning involves many different aspects, including:
CPU and vCPU sizing...
Hi @kaushal_shah , welcome to the forum.
You need to provide more information so that members can help.
Start with:
lsblk
lsscsi
cat /etc/PVE/storage.cfg
pvesm status
Also, review your journalctl output.
Cheers.
Blockbridge : Ultra low...
Hi @gplechuck , welcome to the forum.
Technically, a qcow2 overlay can use a raw image as a backing file. PVE doesn't implement it that way for volume-chain snapshots.
One of the pitfalls of of using RAW vs QCOW base is during creation of a...
Hi @linuxxx3250 , welcome to the forum.
Have you checked the journalctl and dmesg on the PVE host at the time of errors?
In my experience not all NFS servers are created equal. Some struggle with directory listings when a lot of files are...
Hi @jan24, welcome to the forum.
Today, a PVE cluster relies extensively on cross-node SSH communication via root account. While it primarily uses key-based authentication, password authentication is required in some situations, particularly...
Just fyi, PVE8 is less than 30 days from EOL- https://forum.proxmox.com/threads/proxmox-ve-support-lifecycle.35755/
The release notes for 8.4 state: Allow uploading and downloading disk images to storages with content type "Import", in...
Hi @rbremer ,
PBS does not take storage snapshots, perhaps you meant to use a different abbreviation here? Just clarifying this for the whole picture.
Well, this API call is specifically marked as "do not use"...
You run the risk of breaking customer's GUI by introducing patches to the core software product that may conflict with future updates.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Your SDA is divided into 3 partitions (1,2,3) and there appears to be no LVM so pvresize does not apply.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
The historical pitfall with this design is : splitting LUNs across SP A/SP B improves parallelism and queue depth, but if each SP is already running near its own capacity, a failure/trespass event on one SP means the survivor has to absorb both...