Recent content by Ivan Gersi

I`m often using Proxmox in my classic setup, 2 nodes with 1 VM, 1/24h backup to NAS via NFS or CIFS. NASes are added for all nodes via storage menu in Datacenter. And there is a problem. Sometimes node lost connection with NAS and VM is going to be locked and unavailable. I have to restart node...

Of course I did it on node. not on VM. I thought I have to do it this way. Mea culpa. Now it seem to be ok. fstrim -av /: 939.8 GiB (1009099677696 bytes) trimmed

I have node (ext4) with several VM machine. One VM is Debian with 1.4TB disk (Ide, raw). Backup of this machine have still over 1TB despite the fact VM has already only 400GB data. I`ve tried to use trim(fstrim) with this result (discard is checked on VM`s disk). root@pve6:~# fstrim -av...

Of course VM, there is no hardware option in node menu.

This is trivial task but I`m not sure for 100% so I`l like to ask you. If I have a classic servers with several NICs I always try to make ideal settings, so separate network for nodes, corosync, ceph...etc and every network has own physical interface. But this is 2 nodes cluster based on 2...

There are several threads about not comfortable way how to shrink some VM (especially Win VM) with not clear results always. This is my succesful way today. I have 1TB VM Win2019 server but with only 90GB data in. I wanted to resize VM disk from 1TB to 500GB because there is waste time to backup...

I`vè already have changed scsi controller to default (instead virtio), so now I checked discard=on but I thought optimize must do node, not VM. Now, it seems good. Thanks for explanation. Solved

I have Windows VM machine virtualized from physical machine via virtio. I had to reduce lvm size to 1TB because I use 2TB disk for migrating (physical server is only 1TB) There is one problem...I had about 600GB cams recording in the server, so I delete it and server has only 200GB/1000GB...

But this problem is older, from 7v (maybe 6v?).

Solution is very simple...unplug usb during looking for ISO file and plug in again. Working for every versions.

There is problem the same label and same type because I tried to make local on the bot nodes but one node has zfs type and 2nd lvm and migration not worked. I `m only curious now, because backup/restore is more effective for me now (backup (21GB zstd about 5min, restore the same) vs migration...

There are several topics in this forum about this issue but I can`t be able migrate VM from zfs node to lvm node. I`ve tried offline, online, move VM`s disk from zfs to local(dir) with no success. This is my storage. Local-lvm is on pve2, pve1 has zfs FS. I`ve read in this forum there can be...

Thanks aaron, now is cluster online and ready to go.

aaron thanks for hint...this can be problem... and pve2

AarIon I think you``re probably right but tis is my theory...I`ve made node 1 a few weeks ago so I can`t remember configuration exactly... I thought there was the same, but nod1 has 4TB zfs-local and node2 only 1TB. Cluster wanted only one zfs-local but node2 hasn`t enough capacity.and this was...