[systemd] Version 245.6-1 breaks suspended + resume

Sedat Dilek sedat.dilek at gmail.com
Mon Jun 8 13:37:37 BST 2020


On Mon, Jun 8, 2020 at 1:07 PM Michael Biebl <biebl at debian.org> wrote:
>
> Hi Sedat
> Am 08.06.20 um 10:12 schrieb Sedat Dilek:
>
> > Today, I switched over from systemd version 245.5-3 to 245.6-1 on
> > Debian/testing AMD64.
> >
> > On the upgrade, I read there is a new version of journald.conf.
> > I have not checked what changed.
> >
> > Here I have a 00-journal-size.conf file:
> >
> > # cat /etc/systemd/journald.conf.d/00-journal-size.conf
> > [Journal]
> > SystemMaxUse=100M
> >
> > I increased the value for SystemMaxUse from 50M to 100M (see below status).
> > Too small?
> > Unsure, if this is related or not.
>
> Seems unrelated to your problem
>
> > And did a 2nd suspend and resume.
> >>From my memory:
> > Ext4-FS block issues
> > systemd-journald: /var/log/journal/... is read-only
> >
> > The system is in an awful and unusable situation.
> > Typing any command in konsole shows command not known/found.
> > I have not found a way to debug this.
> >
> > Known issue?
>
> The symptoms you see point to a kernel problem / file system corruption
> which are highly unlikely related to the systemd upgrade.
>
> > What informations do you need?
> > Can you give help on debugging?
>
> I think you need help from the kernel folks. I doubt this is a systemd
> issue.
>

Thanks for your feedback, Michael.

What about...

My root-fs is layes on /dev/sdc2 and is mounted like this in

[ /etc/fstab ]

# Root-FS /dev/sdc2
UUID=<UUID-of-rootfs>      /               ext4    errors=remount-ro
    0       1

Can this cause this sort of problems?

- Sedat -



More information about the Pkg-systemd-maintainers mailing list