Comment 87 for bug 1746340

Revision history for this message
Lucas Zanella (lucaszanella) wrote :

The next time it happen I will post the full dmesg. But even my first message (#1):

Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0

cites EXT-4 errors. It's always been like that, nothing changed.

I need to fsck the rootfs now or when the error happens again? And how should I do it?