On Tue, Apr 28, 2020 at 4:37 PM <dhorf-hfref.4a288...@hashmail.org> wrote:
> On Tue, Apr 28, 2020 at 03:26:44PM -0300, Franz wrote: > > > a) check what the actual size is: > > > dom0$ sudo lvs -a | grep yourvmname > > > => whats the size of the yourvm-private volume? > > did it, but there is no unit, so number are difficult to interpreter, > > snapshot enclosed > > not sure what that means. > the "g" in "18.09g" is short for "giga". > and the unit is most likely "bytes". > > so the blockdevice is actualy the right size. > > > > b1) if it is 18GB already, check that it is actualy 18GB inside the vm: > > > yourvm$ grep xvdb /proc/partitions > > same, snapshot enclosed > > the size is again 18.x GB. > > > > > c1) if it is 18GB inside the VM too, you are just missing the fs > resize: > > > yourvm$ sudo resize2fs /dev/xvdb > > Permission denied, see snapshot > > no idea what that means. > but you are using an ancient version of resize2fs there. > > please try with a template/distro that is not shipping outdated versions. > a fedora 30 or 31 should work. > 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. 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. But if this is the case users should be allowed to increase size when the VM is running. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAPzH-qAizhmEvSW_YT-zxxJkmir9JB-frgMpVEwKmw8mFEPrMQ%40mail.gmail.com.
