>>> Franz <[email protected]> schrieb am 29.04.2020 um 20:10 in Nachricht <12446_1588183865_5EA9C338_12446_12_1_CAPzH-qB-p_Q3kCn7kGUE8F4=Bsn4mPPrmU-w76NO0 [email protected]>: > Dear Dhorf, > I tried fsck on dom0, but got the enclosed terror screen. > For me it is enough, I created a new VM, copied content of the old > corrupted one to the new one. Everything works and do not afford to do more > because it is too complicated for my little mind. > But i want to thank you, with your help I understood were the problem is > and for the future I'll avoid to chenge size of a running VM. I understand > it can theoretically be done, but it does not work for me. On the other > hand, it works if the VM is not running. > So thanks Dhorf I appreciate the time you devote for me
Hi! While I'd be able to perform the needed fsck, I wonder: Is it possible to set a flag that makes fsck do a full filesystem check on the next boot? Havent found one for ext3... If the fs tools don't have that feature (yet), maybe it could be build into initrd (some flag just causes a full fsck to be performed before the fileystems are mounted (read-write). Regards, Ulrich > > On Wed, Apr 29, 2020 at 9:42 AM <[email protected]> wrote: > >> 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/CAPzH-qB-p_Q3kCn7kGUE8F4%3DBsn4 > mPPrmU-w76NO0B2L7fYFaQ%40mail.gmail.com. -- 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/5EB0693B020000A100038B7E%40gwsmtp.uni-regensburg.de.
