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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--- Comment #5 from sander44 (ionut_n2001@xxxxxxxxx) ---
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.



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux