| 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
| ||
|
Message-ID: <bug-215879-13602-BHbUUrIQPI@https.bugzilla.kernel.org/> Date: Sun, 19 Feb 2023 14:30:09 +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 --- Comment #5 from sander44 (ionut_n2001@...oo.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.
Powered by blists - more mailing lists