From: Sedat Dilek <sedat.dilek@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-ext4@vger.kernel.org, linux-block@vger.kernel.org
Subject: Linux v5.7.1: Ext4-FS and systemd-journald errors after suspend + resume
Date: Mon, 8 Jun 2020 15:26:40 +0200 [thread overview]
Message-ID: <CA+icZUWuds-wNr+NDVPDaxJ83cmCTPPTZ8qL8U5by2FC1uTHYw@mail.gmail.com> (raw)
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
next reply other threads:[~2020-06-08 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 13:26 Sedat Dilek [this message]
2020-06-08 15:46 ` Linux v5.7.1: Ext4-FS and systemd-journald errors after suspend + resume Sedat Dilek
2020-06-08 17:05 ` Sedat Dilek
2020-06-08 20:21 ` Theodore Y. Ts'o
2020-06-09 4:01 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+icZUWuds-wNr+NDVPDaxJ83cmCTPPTZ8qL8U5by2FC1uTHYw@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).