Linux v5.7.1: Ext4-FS and systemd-journald errors after suspend + resume

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

for a long time I did not try suspend + resume.

So, with Linux v5.7.1 I tried it.

As I upgraded my systemd to version 245.6-1 I suspected this change,
see my report to Debian/systemd team.

Second, as I saw read-only filesystem problems in the logs I changed
in /etc/fstab:

-UUID=<UUID-of-rootfs> /   ext4 errors=remount-ro 0 1
+UUID=<UUID-of-rootfs> / ext4 defaults 0 1

That did not help.

I have one single / root-fs partition.

What 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 <---
Also kded5 etc.

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.

What informations do you need?
Any hints on how to debug this?

Thanks.

Regards,
- Sedat -

[1] https://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/2020-June/041057.html



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux