Re: solution to / full

[Greg Wooledge <greg@wooledge.org>]

On Wed, Mar 01, 2023 at 05:53:18PM -0500, Jeffrey Walton wrote:
> On Wed, Mar 1, 2023 at 8:35 AM lina <lina.lastname@gmail.com> wrote:
> >
> > My / is almost full.
> >
> > # df -h
> > Filesystem      Size  Used Avail Use% Mounted on
> > udev            126G     0  126G   0% /dev
> > tmpfs            26G  2.3M   26G   1% /run
> > /dev/nvme0n1p2   23G   21G  966M  96% /
> > tmpfs           126G   15M  126G   1% /dev/shm
> > tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> > /dev/nvme0n1p6  267M   83M  166M  34% /boot
> > /dev/nvme0n1p1  511M  5.8M  506M   2% /boot/efi
> > /dev/nvme0n1p3  9.1G  3.2G  5.5G  37% /var
> > /dev/nvme0n1p5  1.8G   14M  1.7G   1% /tmp
> > /dev/nvme0n1p7  630G  116G  482G  20% /home
> 
> You can probably reclaim a couple of GB by trimming systemd logs. It
> should get you some room to work. Something like:
> 
>    journalctl --vacuum-time=14d

Aren't those stored in /var, though?  There's a separate /var file system,
which isn't low on space.