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

Message-ID: <bug-215879-13602-hayy4Pm3Jk@https.bugzilla.kernel.org/>
Date:   Mon, 25 Apr 2022 04:12:03 +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
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #3 from Theodore Tso (tytso@....edu) ---
We should really improve the error message; what this indicates is that while
trying to read from a directory, ext4 received an I/O error from the storage
device:

                wait_on_buffer(bh);
                if (!buffer_uptodate(bh)) {
                        EXT4_ERROR_INODE_ERR(dir, EIO,
                                             "reading directory lblock %lu",
                                             (unsigned long) block);
                        brelse(bh);
                        ret = ERR_PTR(-EIO);
                        goto cleanup_and_exit;
                }

I'm not sure why systemd is trying to read so many directories, and why you
aren't seeing any I/O error messages logged on the console.  At a guess, the
block device has completely failed, and there were messages about the unfolding
disaster that has since scrolled off your screen.

Bottom line, this is very likely an hardware problem of some sort.

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

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