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

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200608202115.GH1347934@mit.edu>
Date:   Mon, 8 Jun 2020 16:21:15 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Sedat Dilek <sedat.dilek@...il.com>
Cc:     Andreas Dilger <adilger.kernel@...ger.ca>,
        Jens Axboe <axboe@...nel.dk>, linux-ext4@...r.kernel.org,
        linux-block@...r.kernel.org
Subject: Re: Linux v5.7.1: Ext4-FS and systemd-journald errors after suspend
 + resume

On Mon, Jun 08, 2020 at 03:26:40PM +0200, Sedat Dilek wrote:
> 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.

If you didn't update Othe fstab in the initramfs, the root file system
may still be being mounted with errors=remount-ro.

You can check the current status of a file system's mount options
using /proc/mounts.  Or if you want the full set of changes, you can
look at the file /proc/fs/ext4/<device>/options.

When was the last kernel version and systemd where suspend/resume
worked for you?  If the things work fine until you do a
suspend/resume, this could be either a hardware issue, a driver issue
in the kernel, or systemd issue.  It's almost certainly not a file
system issue, however.  It's likely that you'll need to do a
disciplined set of debugging, where you find which versions of
software work, and then try figuring out what was the first version of
the kernel and/or/systemd where thigns stop working.

					- Ted