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

Date:   Mon, 8 Jun 2020 19:05:53 +0200
From:   Sedat Dilek <sedat.dilek@...il.com>
To:     "Theodore Ts'o" <tytso@....edu>,
        Andreas Dilger <adilger.kernel@...ger.ca>,
        Jens Axboe <axboe@...nel.dk>
Cc:     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 8, 2020 at 5:46 PM Sedat Dilek <sedat.dilek@...il.com> wrote:
>
> On Mon, Jun 8, 2020 at 3:26 PM Sedat Dilek <sedat.dilek@...il.com> 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.
> >
> > 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
>
> I checked the health of /dev/sdc with:
>
> root# badblocks -sv /dev/sdc2
>
> No errors.
>

Just as an information:

The external /dev/sdc hdd is attached to an internal usb-3.0
controller from ASMedia.

- Sedat -