On Monday, December 17, 2018 at 10:40:45 AM UTC+2, awokd wrote: > dimi wrote on 12/17/18 7:03 AM: > > On Sunday, December 16, 2018 at 11:32:57 PM UTC+2, awokd wrote: > >> dimi wrote on 12/13/18 2:10 PM: > >>> Having fun with qubes r4 but can't help myself with this problem. > >>> > >>> sudo lvs, shows me a bunch of deleted VM's that 'seem' to eat up my disk > >>> space. > >>> > >>> > >>> 1) Mostly used Qubes Manager to delete them. How do you delete appVM's / > >>> TemplateVM's the right way so that no zombies will up on sudo lvs? > >>> > >>> 2) Why do i see these deleted VMs in /dev/qubes_dom0/ better yet these > >>> deleted VM's leave stuff / traces on disk in, > >>> /dev/mapper/ > >>> /dev/qubes_dom0/ > >>> /home/XXX/.config/menus/applications-merged/user-vmName-vm.menu > >>> /var/log/qubes/ > >>> /var/log/xen/ > >>> > >>> 3) sudo lvdisplay is showing me backups, vm-<vm_name>-number-back, are > >>> these actual backups? > >>> Aince i do manual backups to another disk, how do i disable these? > >>> > >> 1) Can't recreate- might be an LVS thing. Have you rebooted since > >> deleting the VMs? > >> > >> 2) Same for /dev/mapper and /dev/qubes_dom0. I do see some stale entries > >> in /home/XXX/.config/menus/applications-merged/user-vmName-vm.menu, > >> though. Might be ones I had restored from 3.2. These can probably be > >> safely deleted. Those log files don't get pruned automatically AFAIK, so > >> you will see old entries out there unless you set up a job to > >> periodically delete old ones. > >> > >> 3) Those -back are snapshots kept so you can rollback. See > >> https://www.qubes-os.org/doc/software-update-vm/#reverting-changes-to-a-templatevm-r40 > >> for a little more info. > > > > 1) yes, plenty of reboots have happened > > 2) pure r4 install here, are you suggesting rm command to delete or some > > other qubes command i am not aware of? > > 3) well since i deleted the VM's and/or Templates why would i need to keep > > those snapshots around. How do i correctly remove these? > > 3) > > 1) I usually use qvm-remove to delete VMs, but Qube Manager should do > exactly the same thing. Are you making sure they're shutdown before > deleting? > 2) rm to delete the old menu entries and log files. I guess lvremove to > get rid of the old volumes listed with lvs, my assumption being Qubes > will realize they are gone and handle the entries in /dev/qubes_dom0 > appropriately. Haven't encountered this problem before. > 3) Also lvremove.
1) Yes, VM's are shutdown before removing. I am double, tripple checking before any delete action. 2) ok 3) ok Thank you for teaching me awokd, lvremove /dev/qubes_dom0/vm-leftover-private did it. Will reboot once i am done cleaning up, quiet a few leftovers here. And you are saying that your lvs does not show you any traces of left over VM's? How could i prevent that from future happing? Dreadfully go through a Qubes reinstall, i had some problems with Anaconda and restore backuped VMs? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/afb26bfc-eddf-447f-b1b9-73fd1ff15e16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
