Recent content by Foodrinks

I'm, sure, in version 5.x that was a CLEAN LVM partition with filesystem ext4 (and mounted in fstab). Something was wrong in upgrade to 6.x. What you are suggesting, is what i would have done normally, but, my question is WHY that happened ?

root@comeshost1:~# pvs -a PV VG Fmt Attr PSize PFree /dev/sda2 --- 0 0 /dev/sda3 pve lvm2 a-- 2.18t <15.86g root@comeshost1:~# vgs -a VG #PV #LV #SN Attr VSize VFree pve 1 3 0 wz--n- 2.18t <15.86g root@comeshost1:~# lvs -a LV VG...

I found a strange behavior... In /etc/lvm/backup there are 2 files. root@comeshost1:/etc/lvm/backup# l total 16 -rw------- 1 root root 1642 Oct 27 2017 storage1 -rw------- 1 root root 3378 Feb 10 18:32 pve drwx------ 2 root root 4096 Feb 10 18:32 . drwxr-xr-x 5 root root 4096 Feb 10 21:19 ...

We have updated proxmox 5.x to 6.x (latest upgrade, via pve5to6 and apt-get dist-upgrade). Before, we have removed LVM thin data storage and create a LVM data storage. So, after upgrade to 6.x, booting has a problem (data is for us a directory and mounted in /etc/fstab), and boot stay in...

Thx, there are other tools too: sfill and zerofree .... The only solution.

Thx for the reply, VM disks are VirtIO SCSI "raw", so there is no "thin provisioning" and no "discard" option.....

I have this situation: VM with 2TB disk, and 2 x 500GB disks. The 2TB is the main disk for a debian VM, mainly a Samba fileserver. The 2 x 500GB disks are mounted on the Samba structure for containing files NOT TO BE BACKED UP. So, in VM config, hardware, advanced, i flag the "no backup" option...