>
> On Mon, Nov 29, 2021 at 11:06 AM Patrick Dupre wrote:
> > 631500 /var/tmp/flatpak-cache-LU5PD1
> > 6326584 /var/tmp
>
> This seems like a really good place to start cleaning up. You'e got
> 6GB used in /var/tmp, much of which might be failed flatpak installs?
> https://github.com/flatpak/fl
On 11/30/21 2:57 PM, Jonathan Billings wrote:
The disk images take up space though, and even if you delete them, if
the loopback mount point still is running, the disk space won’t be
available.
Yes, of course. My point was that the loop mount doesn't take up any
new space.
___
On Mon, Nov 29, 2021 at 11:06 AM Patrick Dupre wrote:
> 631500 /var/tmp/flatpak-cache-LU5PD1
> 6326584 /var/tmp
This seems like a really good place to start cleaning up. You'e got
6GB used in /var/tmp, much of which might be failed flatpak installs?
https://github.com/flatpak/flatpak/issues/111
On Nov 30, 2021, at 16:19, Joe Zeff wrote:
>
> Those mountpoints are loop devices
> (https://en.wikipedia.org/wiki/Loop_device) and allow you to treat a disk
> image file as though it were a disk partition. I don't think that they take
> up any more disk space than the file they're mounting d
On 01/12/2021 05:04, Patrick Dupre wrote:
Can somebody tell me what are these files (my drive is a SSD)?
/dev/loop0 63616 63616 0 100%
/var/lib/snapd/snap/gtk-common-themes/1506
/dev/loop1 165376 165376 0 100%
/var/lib/snapd
On 11/30/21 1:32 PM, George N. White III wrote:
The laptop is rebooted twice a day.
Whay should I umount ?
Those mountpoints are loop devices
(https://en.wikipedia.org/wiki/Loop_device) and allow you to treat a
disk image file as though it were a disk partition. I don't think that
they take
Can somebody tell me what are these files (my drive is a SSD)?
/dev/loop0 63616 63616 0 100% /var/lib/snapd/snap/gtk-common-themes/1506
/dev/loop1 165376 165376 0 100% /var/lib/snapd/snap/gnome-3-28-1804/128
/dev/loop2
On Tue, 30 Nov 2021 at 04:15, Patrick Dupre wrote:
> Sorry, but I need to do something,
> now / is really full.
>
> The laptop is rebooted twice a day.
> Whay should I umount ?
>
> What are all these
> /dev/loop0 6361663616 0 100%
> /var/lib/snapd/snap/gtk-com
Sorry, but I need to do something,
now / is really full.
The laptop is rebooted twice a day.
Whay should I umount ?
What are all these
/dev/loop0 6361663616 0 100%
/var/lib/snapd/snap/gtk-common-themes/1506
/dev/loop1 165376 165376
On Nov 29, 2021, at 16:14, Patrick Dupre wrote:
>
> But the why /var requires so much of room.
> I would like to find a temporally solution to avoid a crash.
Judging from the output of your df command, it is most likely snaps that are
taking up a lot of space. I’ve seen that quite often. Even
I can certainly fix the issue properly, but not when I am out of town
and when I need my laptop.
But the why /var requires so much of room.
I would like to find a temporally solution to avoid a crash.
> Subject: Re: disk full
>
> On 11/29/21 12:33 PM, Patrick Dupre wrote:
> &
On 11/29/21 12:33 PM, Patrick Dupre wrote:
/dev/mapper/VolSys1-root 56635708 52977980757768 99% /
I can see why you're so concerned. You appear to be using LVM; is there
any free space in the volume that can be used here? It's probably only
a stopgap, but it should give you more time
> Sent: Monday, November 29, 2021 at 9:30 PM
> From: "Joe Zeff"
> To: users@lists.fedoraproject.org
> Subject: Re: disk full
>
> On 11/29/21 12:06 PM, Patrick Dupre wrote:
> > No,
> >
> > /boot is on a separated partition.
> > I am ta
On 11/29/21 12:06 PM, Patrick Dupre wrote:
No,
/boot is on a separated partition.
I am talking about /
(/home is on a separated partition).
(same thing for /usr/local /usr/src)
In addition, I noted
OK, that tells us where the congestion is, but not how bad it is. What
do you get from
df /
>
>
> On Mon, 2021-11-29 at 18:58 +0100, Patrick Dupre wrote:
> > Hello,
> >
> > Is there a good reason to have my drive (system) full since this WE.
> > the new kernel?
> >
> > Is there an easy way for temporally avoid any problem?
> > I am out of town, and I do not want to challenge my distribut
On Mon, 2021-11-29 at 18:58 +0100, Patrick Dupre wrote:
> Hello,
>
> Is there a good reason to have my drive (system) full since this WE.
> the new kernel?
>
> Is there an easy way for temporally avoid any problem?
> I am out of town, and I do not want to challenge my distribution right
> now.
>
Hello,
Is there a good reason to have my drive (system) full since this WE.
the new kernel?
Is there an easy way for temporally avoid any problem?
I am out of town, and I do not want to challenge my distribution right now.
Thanks
=
17 matches
Mail list logo
