Search results

Wenn einer VM 4GB RAM zugewiesen werden und auch dessen Minimum auf 4GB gesetzt wird, dann spielt Ballooning nur noch eine Nebenrolle. Ballooning dient in diesem Fall "nur" noch der Informationsbeschaffung über die derzeitige RAM-Auslastung des Gasts...

I'm sorry but maybe you can mount/repair your volumes when booting from a live USB stick (e.g. Debian or easier Ubuntu). When successful you can backup your needed data and reinstall Proxmox VE. It's a bit of work and learning but that's probably your best choice to get a well working default...

A "physical PBS" is how it's designed for, in combination with an SSD and a good network connection you can expect quite fast backups. What's the storage type of 'DDBackups' and how is it connected? pvesm status How is your PBS connected and how does the host system of your PBS looks like?

"Very slow" depends on many factors but your post doesn't provide more information about hardware/software configuration. Since the average rate of 135.9 MiB/s doesn't seem reasonable for you, can you also provide stats with the aforesaid compression turned off? What did you try so far? Maybe...

On a normal ext4 mounted filesystem you could well use testdisk/photorec, but that's unfortunately not possible in this case with fuse/sqlite (db located in /var/lib/pve-cluster - but without a backup not helpful). Without a (recent enough) backup there's likely not much you can do about. mount...

They started and were successful, so no issues arose. Anyway, I've used a different and beta version for testing, sorry.

Why trying this? If successful you would lose all your VM and snapshot data. Start with freeing space on your pve-root.

https://pbs.proxmox.com/docs/proxmox-backup.pdf#1c Although the performance-wise best solution (in the long run) would be to change your setup to installing PBS directly on a host with the provided installer-image, you can still try to improve your setup by adapting it to...

Please post also: PVE: qm config <vmid> # from PBS and one large guest cat /etc/pve/storage.cfg journalctl -u pvedaemon.service # something interesting? PBS: cat /etc/proxmox-backup/datastore.cfg mount | grep -e mapper -e mnt Since you use an unrecommended setup (PBS as VM, HDD as backup...

I've tried to reproduce this on proxmox-ve: 8.0.0 (running kernel: 6.2.16-1-pve) pve-manager: 8.0.0~8 (running version: 8.0.0~8/708b186d18a76e28) Backup Server 2.4-1 but the scheduled task runs successful again as expected. I've changed the IP on PBS via WebUI (Configuration >...

1. The allocated (first value) and the actual size (second) can be displayed with: ls -slh 2. How much data you can really store inside a qcow2 image depends also on things like compression, copy-on-write or the used filesystem inside. Regarding the lack of free space you can also read about...

Look for M.2 SSDs with power-loss protection, e.g.: https://skinflint.co.uk/?cat=hdssd&xf=4832_3%7E4832_4

Strange that there's no trace from the logical volume 'vm-101-disk-0'. lsblk lvs lvscan should list them if they are existing. Maybe you accidentally attachted a wrong disk or overwrote your original setup?

Your config vgname mismatches with the actual vgname. vgrename pvedata jlm_photos should solve the issue.

Can you post the jlm_photos section from /etc/pve/storage.cfg

There's the command vgrename with an example: You've duplicated VG names in the metadata, I doubt that your applied commands will solve your issue. Maybe it's "better" to revert your changes from 'pve1' back to 'pve' since it's the default name and afterwards change the VG name of your...

Please post: vgdisplay Your pve-root is 95% filled with 0 FSAVAILABLE? lvconvert --repair calls thin_repair. man thin_repair states that it's important to have enough space left for metadata - maybe that's the issue?