apt full-upgrade causes system lock-up

Colin Law clanlaw at gmail.com
Fri Jun 3 14:23:22 UTC 2022


On Fri, 3 Jun 2022 at 14:57, Bo Berglund <bo.berglund at gmail.com> wrote:
>
> On Fri, 3 Jun 2022 12:12:45 +0100, Colin Law <clanlaw at gmail.com> wrote:
>
> >On Fri, 3 Jun 2022 at 11:40, Liam Proven <lproven at gmail.com> wrote:
> >>
> >> Bo, do you schedule `trim` on your SSDs? If not, you should.
> >
> >I believe it is scheduled weekly by default on standard Ubuntu at
> >least.  This command should confirm that:
> >systemctl status fstrim.timer
> >
> >Colin
>
> $ systemctl status fstrim.timer
> ? fstrim.timer - Discard unused blocks once a week
>      Loaded: loaded (/lib/systemd/system/fstrim.timer; enabled; vendor preset:
> enabled)
>      Active: active (waiting) since Thu 2022-06-02 07:37:07 CEST; 1 day 8h ago
>     Trigger: Mon 2022-06-06 00:00:00 CEST; 2 days left
>    Triggers: ? fstrim.service
>        Docs: man:fstrim
>
> Jun 02 07:37:07 aspomint systemd[1]: Started Discard unused blocks once a week.
>
> Is this what it should look like?

Yes

> I have another drive connected to the system, a 2TB 2.5" HDD mechanical drive.

What does this command show?
df -xsquashfs

The -xsquashfs stops it spamming the output with snap mounts.

Colin




More information about the ubuntu-users mailing list