You can run chattr +i /mnt/unaspro while unmounted to prevent this from happening again. See here: https://serverfault.com/questions/570255/prevent-the-possiblity-of-writing-data-to-an-unmounted-mount-point-directory
That helped. I unmounted the network share, restarted the vm, then used the gdu tool to drill down and delete everything under /mnt (16 GB of data found there ), then remounted the network share. All good. thx to you guys. @Impact @Onslow
I created a few backups on the local disk before setting up an nfs share for future backups. I forgot to delete my old backups. Now, my boot disk seems full ( 32G ). How do I clean up the old backups on this disk?
proxmox-backup-manager...
@aaron Node 1 is the main workhorse - with tons of VMs on it. It also has another truenas vm running there too. It will be much simpler for me to clear the VMs on node 2. How will the backup and restore work in this case?
Update:
--
It seems I...
Looking to create a cluster with two existing standalone nodes ( with VMs on them) and a new third node. The second node has a truenas vm, using 4 pci passed through disks. I am not entirely sure how to handle this when adding the node to the...