Search results

Could you please share the steps, how you have installed btdu, I tried it and seems not working

HI, THere is nothing to delete, confirmed everything.

HI, We have thoroughly checked and confirmed that no backup snapshots are stored in the storage. There is only one VM, which is using 6 TB, but the remaining usage is still unexplained. btrfs fi usage / Overall: Device size: 18.19TiB Device allocated...

We have a single-node Proxmox setup with one VM, which is a Proxmox Backup Server. The node has a total storage capacity of 20 TB, of which 14 TB is allocated to the VM. Currently, the VM has used 6 TB of storage, leaving about 8 TB available within the VM. However, Proxmox VE is showing a...

Hi Support, In our proxmox node, the VMs are configured with a network limit of 12.5 Mbps, but we’ve observed it occasionally exceeding this limit and reaching up to 20 Mbps. How is this possible? Can anyone advise what could be the reason for this? much appreciated Thank you.

Hi, I would like to kindly ask if there is a way to check whether fleecing backup is currently in use on my proxmox. Additionally, I would appreciate any guidance you could provide on how to set up fleecing backup on an already running Proxmox. Thank you.

Hi Support, The PBS is an external server, and the backup was running on that external server. Could you please provide the reason for this issue? Thank you.

Hi Support, The server became unresponsive while a PBS backup was running. I stopped the backup, and the server is now functioning again. It seems the backup process caused the issue. Could you please look into this and assist Thank you.

It was some time ago, I think the snapshot deletion interrupted highway on the first time, and it is the issue, how can we fix it now

Below is the config, cat /etc/pve/qemu-server/112.conf agent: 1 boot: order=sata0 ciuser: root cores: 2 efidisk0: px-st:vm-112-disk-4,efitype=4m,pre-enrolled-keys=1,size=1M ide0: px-st:vm-112-cloudinit,media=cdrom,size=4M ide2: NFS:iso/CentOS-7-x86_64-Minimal-1810__2_.iso,media=cdrom,size=918M...

We have server with the id 112 and snapshot named "BeforeDiskUpgrade", when I try to delete the snapshot getting the error as "rbd error: rbd: error opening image vm-112-state-BeforeDiskUpgrade: (2) No such file or directory", I tried to check from the snapshot from pool but it doesn't exist...

Hi, May I know if anyone did follow this documentation? and will this work? Also, is recommended? will affect proxmox function? https://pve.proxmox.com/wiki/User:Grin/Ceph_Object_Gateway Thank you.

Strange, I managed to fix it by running the command "reweight-by-utilization" , not sure why, but it fixed the issue

HI, we have Proxmox VE Community Subscription till now, and it expired, the PVE version is 8.1.3, now we need to upgrade the PVE with pve no subscription, will this work? or will have any conflict issues? Thank you.

HI, All of the OSD disks are HDDs and the network port is 10 Gbps, the issue was only present recently, there was no issue before. I know HDD is slower, we use this cluster for storage purpose only , but it seems like unrelated to the issue. There is a total of 1025 PGs and the issues only...

Despite altering the values and seeing scrubbing processes in progress, the warning about 621 unsscrubbed and not deep scrubbed pgs persists. I cannot determine the cause of this discrepancy yet. no idea

I couldn't understand the recommended configuration, can anyone advise the same, we have 7 node cluster with 35 ODSs Thank you

Hi, There are sufficient resources in the server and bandwidth, we have checked and there is no bandwidth limitation. Thank you.

Hi, Today, I removed a snapshot from a VM (2TB storage )in the Proxmox cluster. Shortly afterward, Ceph started rebalancing, causing all VMs to go down until I halted the removal process and the rebalancing was completed. What might have caused this issue?

We’ve been receiving warnings about 621 PGs not being deep-scrubbed and 621 PGs not being scrubbed in time for a while now, and the issue doesn't seem to be resolving. Is there a command that can address this problem? There are over 600 PGs showing this error—will manually scrubbing each PG...