Search results

Edit: Actually, ignore the below. Somehow, running fsck a second time worked... thanks again! Thanks, I finally got around to trying this. I booted to a GParted Live CD and ran fsck, but unfortunately it fails without much further information. Is there anything else I can try to fix this...

I had a power outage the other day, and now when I boot one of my VMs, I get file system errors. Unfortunately, fsck from the host doesn't work, it complains about an invalid superblock: root@pve:~# fsck /dev/mapper/pve-vm--101--disk--0 fsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021)...

Thanks, this makes sense and it looks like ballooning is working correctly. Cheers

Ah, that's too bad. I used the defaults which I think fully allocated the volume.

Ah I see. I gave balloon 1000 a try and it hasn't increased so I'm not sure that it's working. The configuration is Memory: 2048, Minimum memory: 2048, Ballooning Device: Checked. # info balloon balloon: actual=1000 max_mem=2048 total_mem=945 free_mem=21 mem_swapped_in=483526197248...

Basically, I borrowed these instructions from serverfault.com. But once I got to the fsck step I started getting errors like `ext2fs_open2: Bad magic number in super-block`. Are these steps necessary for the thin pool? There's no filesystem for it to resize, is there? It shows the correct size...

Thanks all. The Ballooning Device checkbox is ticked. I have a VM configured with 2GB of memory. I don't see a change when I use the `balloon <memory in KB>` command. # info balloon balloon: actual=2048 max_mem=2048 total_mem=1993 free_mem=19 mem_swapped_in=80781312 mem_swapped_out=291606528...

I have qemu-guest-agent installed and enabled. Is there something else needed for memory ballooning to work correctly on Alpine? I'm seeing 96%+ RAM utilization with no effect.