On Wed, Apr 29, 2020 at 08:11:37AM -0300, Franz wrote: > Did it with Fedora 30, but with exactly the same result > But checking other VMs I am getting the same error on some of them :(( > So this is a widespread problem.
did you try to google your problem? because at this point it is starting to look less of a qubes problem, and more like generic filesystem damage. fsck+repair the volume, then resize it. consult the documentation of your favorite distro template on how to do this inside the vm. you may have to connect to the vm through "xl console" in dom0. or spawn a fsck-vm, and temporarily attach the volumes to that. https://www.qubes-os.org/doc/mount-lvm-image/ or just fsck+resize from dom0 if you consider the risk of something exploiting e2fstools through this acceptable. > May it be that this is caused by running Qubes manager / vm settings/ > increase private size when the VM is running? Sometimes I get an error on > that. It may be that this creates a problem that cannot be removed. no, online resize is completely normal and supported. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200429124205.GK935%40priv-mua.
