[systemd] Version 245.6-1 breaks suspended + resume

[Sedat Dilek]

> > > 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?
>

I changed this line to...

UUID=<UUID-of-rootfs>   /   ext4   defaults   0   1

...the issue still remains.

I still see after suspend (45 secs) and resume:

Ext4: ... unable to read itable block
Ext4: ... dx_probe:768 ... error read-only directory block
Ext4: ... ext4_get_inode_loc ...
systemd-journald: Failed to write entry - Read-only file system

I will contact linux-ext4 and linux-block maintainers.

Thanks.

- Sedat -