On Mon, May 04, 2020 at 09:12:59PM +0200, Ulrich Windl wrote:
> Is it possible to set a flag that makes fsck do a full filesystem
> check on the next boot?
> Havent found one for ext3...
use tune2fs to set the current-mountcount (-C) to something bigger
than the max-mountcount (check with -l,
>>> Franz <169...@gmail.com> schrieb am 29.04.2020 um 20:10 in Nachricht
<12446_1588183865_5EA9C338_12446_12_1_CAPzH-qB-p_Q3kCn7kGUE8F4=Bsn4mPPrmU-w76NO0
2l7fy...@mail.gmail.com>:
> Dear Dhorf,
> I tried fsck on dom0, but got the enclosed terror screen.
> For me it is enough, I created a new VM,
On Wed, Apr 29, 2020 at 3:27 PM wrote:
> On Wed, Apr 29, 2020 at 03:10:48PM -0300, Franz wrote:
>
> > I tried fsck on dom0, but got the enclosed terror screen.
>
> it would have helped if you had tried to fsck the right filesystem:
> fsck /dev/qubes_dom0/vm-per-dec-private
>
> and if it
On Wed, Apr 29, 2020 at 03:10:48PM -0300, Franz wrote:
> I tried fsck on dom0, but got the enclosed terror screen.
it would have helped if you had tried to fsck the right filesystem:
fsck /dev/qubes_dom0/vm-per-dec-private
and if it is asking for repair a bazillion times, perhaps with
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
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
On Tue, Apr 28, 2020 at 4:37 PM 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
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
On Mon, Apr 27, 2020 at 09:06:41PM -0300, Franz wrote:
> So, it seems that Qubes Manager, Nautilus and df are consistent, telling
> that available space is almost 5GB totally used.
>
> But Qubes VM settings with Private Storage Max Size of 18524 MB is totally
a) check what the actual size is:
Hello all,
Various application lament lack of disk space in a particular qube, but
measuring it gives very different results.
1 Qubes manager tells that Disk Usage is 4973 MB
2 Setting tells that Private Storage Max size is 18524 MB
3 Baobab tells 2.1 GB available and 12.4 GB total
4 Nautilus
10 matches
Mail list logo
