Search results

I think I cannot run pve inside pve because I run proxmox inside a kvm, because I only need containers. That kvm has nested virtualization disabled. Or can you install pve inside a container? If so, I still can't follow your mind, what exactly do I have to do?

And how to do that? In the webinterface you cannot choose a filesystem. And what does LVM has to do with this? I cannot add more space to the proxmox node itself, only space which gets applied over the network (like nfs)

Wenns nur einmal sein soll, um proxmox neu aufzusetzen, mach doch einfach das backup lokal und schiebs dann via scp woanders hin.

Hi, this is a (kind of a) continuation of this thread: https://forum.proxmox.com/threads/container-shows-wrong-disk-usage.37429/ But to keep things clear and because of a new problem I open a new topic. So the old problem was, that whenever I delete files inside a container the raw disk file...

Moin, bei der Installation von proxmox werden ja automatisch zwei storages angelegt, ein folder für VZDump backup file, ISO image, Container template und eine lvm-thin für Disk image, Container. Da ich nur 60GB SSD habe, macht diese unterteilung für mich keinen sinn. Kann man auch nur ein LVM...

For simplicity I just used "folder". Is there any major advantage in using lvm-thin?

Yep exactly i tried to install it on 'local', but thats not for containers or disk images, so I'llt try that with lvm, thanks

Hi, I have debian 9 and installed proxmox like this: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch when i want to create a container i get this error: TASK ERROR: no such volume group 'pve' I added the node to an existing proxmox cluster

So apt upgrade && apt upgrade and i'm done? No need to reboot, no need to stop/restart all VMs/CTs?

I think I'll just use esxi and get away from containers :(

Ok I now did pct mount $vmid and fstrim /var/lib/lxc/$vmid/rootfs for every single vm and i got my disk space back is there any way to do this automatically? did this happen because the containers are unprivileged? edit: ok no the container which freed like 50GB is privileged

root@limone:~# pvs PV VG Fmt Attr PSize PFree /dev/sda3 pve lvm2 a-- 311.75g 15.79g root@limone:~# vgs VG #PV #LV #SN Attr VSize VFree pve 1 16 0 wz--n- 311.75g 15.79g

I know, but I deleted the container 200 and "lvs" dont show vm-200-disk-1 anymore but disk usage is still ~200GB, after deleting this container nothing changed in total disk usage. As you can see I can only write 13 more GB and if I delete something nothing gets freed, so its a race against...

I deleted the container now and the disk space is still used..

In the container there is no output, on the host node there are some files, but not many and theyre not big, 5MB max.

Nothing changed :(

I've run fstrim / but df -h still states Filesystem Size Used Avail Use% Mounted on /dev/mapper/pve-vm--200--disk--1 98G 58G 36G 62% /

What is this option now called exactly? Trim? Discard? In Proxmox I cannot find such an option..

root@test:~# mount /dev/mapper/pve-vm--200--disk--1 on / type ext4 (rw,relatime,stripe=32,data=ordered) none on /dev type tmpfs (rw,relatime,size=492k,mode=755) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) proc on /proc/sys/net type proc (rw,nosuid,nodev,noexec,relatime) proc on...

I dont think so, as i dont have anything i /etc/fstab and the disk space is still used after a reboot, I really dont think so. any way to check this? heres a screenshot of my lvm I dont use 200GB by far, i'd guess something like 100 GB should be the real value. Edit: even 100GB is high, more...