Search results for query: shrink

Thanks. The old machine is not running anymore. What is the solution now?

I did migrations recently and used /usr/sbin/qm remote-migrate However, both machines were running proxmox. One machine, the sender, did have thin drives and the receipient server did not. After tha transfer I did a qemu-img convert -c -O qcow2 to shrink the drive down. HTH

...try it soon, and compare vs gfs2 && ocfs2. The only diff vs ovirt, is that proxmox use internal snapshot, I don't known it's playing fine with qcow2 on blockdevice. (That's also mean than we can't shrink blockdevice after delete of the snapshot) https://bugzilla.proxmox.com/show_bug.cgi?id=4160

And a warning again, as this is a destructive command: If you shrink a virtual disk without shinking its partitions and filesystems first, you will lose data. If you want to shrink it by 34GB, the last 34GB should be unallocated on that LV.

...able to rebalance to a full healthy cluster while you repair/replace the failed OSD/Host (you will lose gross capacity, so net capacity will shrink too). PVE shows the gross space as it can't know how you will use it: the replica/min_replica of your pool(s) or if you use inline compression...

Yes, that makes sense. I just did the default Ubuntu install without thinking about it.

...I would give some consideration to re-architecting it. You don't need LVM in a VM. Give each LVM partition its own virtual disk (and use ext4, since XFS can't shrink) and resizing should be much easier for you in the future. You can even boot something like systemrescuecd and do it in gparted.

...that this option be exposed to the GUI in the restore dialog as it would make the option more accessible. Users could also use the option to shrink the volume if they had made it too large without having to edit the pct.conf then backup and restore. Thanks for reviewing my feature request.

...https://www.usenix.org/system/files/login/articles/140-hellwig.pdf PROTIP - if for some reason you find a need to shrink an XFS filesystem, you can back it up with fsarchiver and then restore it with same - it can convert XFS to ext4 on the fly(!) and all you should need to do is change...

Yeah, that's a surprising failure point with XFS. They designed a (production oriented!) filesystem that can only be expanded, never shrunk. I used to be positive on XFS, right up until hitting this specific issue. :(

...As a sysadmin, I hate the whole idea of LVM in a VM environment. Separate disks instead of playing around with resizing partitions is easier; just don't use XFS if you ever anticipate having to shrink the FS. Expansion is way more common these days tho

Interesting, so is there any point to turning min and max for ZFS then since it will pull from the ZFS arc? or should I then really be setting a min that adheres to the 4GB + 1GB/1TB rule? That way no VM will hijack the memory allocated to ZFS arc, thereby reducing performance?

...the 2 new 180gb drives is a little off putting. I've cloned disks before but only going to the same size or larger. I understand the risks of shrinking a volume so my process would likely be to clone the Proxmox drive to a larger drive first, keeping the original safe, then shrink the size...

> I will check the docs if I can also just shrink the ZFS volume down to 900G as well because I really don't need the storage, or if this always needs a new volume and send/receive or rsync all the data DO NOT TRY THIS WITHOUT A BACKUP, but I just tested this with a file-backed pool on zfs...

...thin provisioning, and added the second disk without replication and everything works like a charm. I will check the docs if I can also just shrink the ZFS volume down to 900G as well because I really don't need the storage, or if this always needs a new volume and send/receive or rsync all...

...system actually runs out. However, it is more likely that your VM won't start in my experience. Yes, ZFS won't free up more memory in that case. So it won't shrink below these 16 GB [1]. [1]: https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#zfs-arc-min

Hello everyone,I need help decreasing disk space. I have a virtual machine with Windows Server 2022, if I shrink the disk from the operating system, is there a way to tell ProxMox that it must only remove the unused part? Thanks

Hello, I want to shrink the size of a vm from 100G to 30G. I booted the vm into gparted and resized the partition to 29G I shutdown the vm ran "zfs set volsize=30G rpool/data/vm-201-disk-0" to leave a little overhead ran "qm rescan" and got the message that the disk-0 has no 30G instead of...

Even if it were possible to shrink (which it maybe) - you wouldn't want to do anything like that on a failing drive. First thing is to make sure you have (external) backups of all VMs & LXCs. These are ALWAYS necessary & a must have on any system. Take note/backup of any personal changes you...

...the 2nd node with ext4+LVM. Rerun the installer on node 2 and select ZFS RAID0 if you're not doing a mirror setup. Alternatively you could shrink partition 4, create partition 5 and create a zpool on it from commandline, but reinstalling is arguably easier if it's a fresh node with nothing...