Search results for query: shrink

My PBS is using around 13TB on my datastores but on the proxmox host on ZFS its using 31TB how is this correct? STORAGE-VM/vm-3016-disk-0 8.88T 6.52T 8.88T - STORAGE-VM/vm-3016-disk-1 16.8T 6.52T 16.8T - STORAGE-VM/vm-3016-disk-2 5.63T 6.52T 5.63T - Can i shrink my ZFS?

@waltar You cannot easily shrink thin pools like pve/data. @dachga You can create a LV inside thr thin volume though and use that.

Correct. And also for completeness, to shrink an LXC disk on zfs: zfs set quota=<new size> <disk dataset> zfs set refquota=<new size> <disk dataset> pct rescan Example: root@richie:~# grep subvol /etc/pve/lxc/999.conf rootfs: local-zfs:subvol-999-disk-0,mountoptions=noatime,size=4G...

...this with the conclusion I reached. The GNS3 OVA is released with a 500GB disk by default. I have not been able to find an easy solution to shrink that disk. The reason I thought the VM is taking up my entire drive is because my drive is a 512GB M.2 drive, so it was taking up all the space...

...Some of these VMs have disks sized at 100GB, but the actual used space is much lower (e.g., 20–30GB). We'd like to migrate these VMs to the second node but shrink the disk size during the migration (e.g., from 100GB to 50GB). What would be the correct and safest way to do this in Proxmox?

...ballooning kicks in. For this reason I try to stay below "80 % used" on the host... Edit: regarding ZFS ARC: yes, it is dynamic and it will shrink "automatically". The problem is that this needs some time. For a process/VM in need of RAM now! this often is too slow --> killing the process...

...mentioned compression - if you have compression enabled on ZFS while having a vm with db on top of it and thinking of extreme performance ... shrink is two doors down the hallway. High load DB with lots of data is worse case scenario for anything, so you should be eliminating layers, not...

Shrink the second (swap) partition (and shift it towards the end) to make space for growing the first partition? This would be simple with booting the system with a GParted Live USB-stick except for the (unsupported by Proxmox) RAID configuration, with which I have no experience.

That is normal - the raw format is not thin-provisioning. To make that file smaller, you basically need todo 3 things: 1. Shrink the VM's partition within that raw file (safely!) to the required size. 2. Truncate that raw file to its correct size. 3. Do a qm rescan --vmid <VMID> to inform...

...is the meaningful metric, hypervisor level view is limited to (active pages). if the workloads are active (in production), you may even shrink RAM definition/assignment to the VM (look at the "available" column and decide how near 0 you are comfortable with) Unrelated note, but stings me in...

...requests. It becomes a bit more complex when you add 4 and 5 nodes, because ideally, you will have the same calculation, however, when a node fails, your blocks are re-allocated on other nodes to restore to size=3, meaning when a node goes down you effectively shrink your available storage.

...add it to the VM, size of the new disk has to be at least the size of the used space on the old drive. 2) Boot into VM. $ cfdisk /dev/source shrink to match (Possibly slightly bigger), do not do this in live environment because it will not boot. 3) Go back to liveCD. $ sgdisk --backup=table...

You need to explain more. What exactly did you do? Did you resize the VM disk at the host level, or in-vm? Are you trying to shrink, or resize-up?

...is somewhat cumbersome and rough. I have a cron job tar-balling the entire /etc + /var/lib folders for backup purposes. I've had a gander at shrinking the boot partition(s) on gparted, but it won't let me shrink the massively large (and largely empty) non-boot partition on the boot drive...

The VM, which is a Win7, doesn’t use the full 500GB. In fact, I’ve reduced the disk space in Windows to 290GB, yet it still won’t let me shrink it. I’m attaching two screenshots to explain better.

...when the VM’s filesystemmarks blocks as unused after deleting files, the controller will relay thisinformation to the storage, which will then shrink the disk image accordingly.For the guest to be able to issue TRIM commands, you must enable the Discardoption on the drive. Some guest...

...taking up space in this drive. I've cleared up about 6gb of storage on this drive by deleting some old data. In disk management if I try to shrink it, it seems to think it can only shrink it by as much data as I've freed up. I guess this has been an issue for a while now, maybe always? A...

Nah, I'm not going to drop ZFS; just frustrated at discovering another ZFS tax. Been hoping to downsize my infrastructure, but ish like this keeps it bloated

Really? Each and every filesystem needs buffers and caches. ZFS is just more clever and makes potentially use of more RAM. (You may shrink it drastically...) If you are going to drop ZFS read this first: https://forum.proxmox.com/threads/question-about-file-system.159762/post-733718

...from `parted -l` and it seems the disks I want to resize are dev/mapper/pve-root: 64.2GB and Disk /dev/mapper/pve-data: 121GB. I want to shrink the `pve-root` partition and create more space for the `pve-data` partition. Will it be safe to use GParted for the resizing? From what I see those...