linux-ext4 - [Bug 215879] EXT4-fs error - __ext4_find_entry:1612: inode #2: comm systemd: reading directory lblock 0

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] [day] [month] [year] [list]

Message-ID: <bug-215879-13602-OnrqXzrHTo@https.bugzilla.kernel.org/>
Date:   Sun, 19 Feb 2023 23:16:14 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 215879] EXT4-fs error - __ext4_find_entry:1612: inode #2: comm
 systemd: reading directory lblock 0

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

Theodore Tso (tytso@....edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #6 from Theodore Tso (tytso@....edu) ---
Note that what you found in your stack exchange search was from five years ago,
and described a workaround in a Linux kernel versiojn 4.10.   In addition to
manually disabling APST (a quirk for a very specific Samsung SSD which has
since been added to newer kernels), other suggestions in the stack exchange or
linked web pages included " removing SDD, blowing air into M.2 connector and
reinserting it back" and "switching off the 'UEFI Secure Boot' setting in the
BIOS"

All of which is to say that the symptom is caused by an I/O error, and there
are many potential causes for an I/O error --- everything from missing quirks
(to work around broken firmware / hardware design) to bad connections to
misconfigured BIOS settings to just plain broken hardware.

This is why blindly web searching based on symptoms can often lead to
misleading results; an abdominal pain could mean anything from indigestion, to
a pulled muscle, to an infected appendix, to a heart attack.  It's also why I
am not fond of people finding bug reports on the web and assuming that anything
that has the same symptom must have the same root cause.....

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

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