All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 215879] EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0
Date: Sun, 19 Feb 2023 14:30:09 +0000	[thread overview]
Message-ID: <bug-215879-13602-BHbUUrIQPI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215879-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215879

--- Comment #5 from sander44 (ionut_n2001@yahoo.com) ---
Hi,

I notice today this issue with 6.1.12 kernel version.

On Ubuntu Team, i view this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993205

But with my search i view workaround: 
https://unix.stackexchange.com/questions/375450/random-ssd-turn-off-ext4-find-entry-reading-directory-lblock0
https://askubuntu.com/questions/905710/ext4-fs-error-after-ubuntu-17-04-upgrade

Will try with this: nvme_core.default_ps_max_latency_us=200 for testing this
issue and to see if it reproduces.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-02-19 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 15:20 [Bug 215879] New: EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0 bugzilla-daemon
2022-04-24 15:23 ` [Bug 215879] " bugzilla-daemon
2022-04-24 15:31 ` bugzilla-daemon
2022-04-25  4:12 ` bugzilla-daemon
2022-05-26 19:18 ` bugzilla-daemon
2023-02-19 14:30 ` bugzilla-daemon [this message]
2023-02-19 23:16 ` bugzilla-daemon

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=bug-215879-13602-BHbUUrIQPI@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.