lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 8 Jun 2020 15:26:40 +0200
From:   Sedat Dilek <>
To:     "Theodore Ts'o" <>,
        Andreas Dilger <>,
        Jens Axboe <>
Subject: Linux v5.7.1: Ext4-FS and systemd-journald errors after suspend + resume


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?


- Sedat -


Powered by blists - more mailing lists