nvme unpredictibly disappears after some time

[Robin Hoizey]

Hi,

I have a Lenovo E15 Gen 2 laptop, bought around 1 month ago, runnning Ubuntu 20.04 (kernel 5.8.0-48-generic)

In this Pc, I have a 512 GB nvme running fine, and a 1TB nvme which somehow disappears after some time.

Let's I turn on the PC, use it for development, word processing, nothing heavily sollicitating the storage, and after some unpredictable time, the PC freezes, and when it comes back to life, the nvme is unmounted and does not appear anymore until I reboot.

I read bug #1910866 which looks very similar, but it is supposed to be fixed in kernel 5.8.0-41.46. As i'm facing the problem with kernel 5.8.0-48-generic, I think it may be another bug.

In the output of journalctl, I see this from april, 8th (filtered on kernel messages):

avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 576 QID 6 timeout, aborting
avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 577 QID 6 timeout, aborting
avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 578 QID 6 timeout, aborting
avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 579 QID 6 timeout, aborting
avril 08 20:38:09 Auckland kernel: nvme nvme0: I/O 468 QID 2 timeout, reset controller
avril 08 20:38:40 Auckland kernel: nvme nvme0: I/O 1 QID 0 timeout, reset controller
avril 08 20:40:12 Auckland kernel: INFO: task jbd2/nvme0n1p1-:546 blocked for more than 120 seconds.
avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu
avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
avril 08 20:40:12 Auckland kernel: jbd2/nvme0n1p1- D 0 546 2 0x00004000
avril 08 20:40:12 Auckland kernel: Call Trace:
avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60
avril 08 20:40:12 Auckland kernel: ? percpu_counter_add_batch+0x50/0x70
avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0
avril 08 20:40:12 Auckland kernel: io_schedule+0x16/0x40
avril 08 20:40:12 Auckland kernel: rq_qos_wait+0x106/0x180
avril 08 20:40:12 Auckland kernel: ? __wbt_done+0x40/0x40
avril 08 20:40:12 Auckland kernel: ? sysv68_partition+0x290/0x290
avril 08 20:40:12 Auckland kernel: ? wbt_cleanup_cb+0x20/0x20
avril 08 20:40:12 Auckland kernel: wbt_wait+0x9e/0xe0
avril 08 20:40:12 Auckland kernel: __rq_qos_throttle+0x28/0x40
avril 08 20:40:12 Auckland kernel: blk_mq_make_request+0xfa/0x5f0
avril 08 20:40:12 Auckland kernel: generic_make_request+0x2b1/0x3b0
avril 08 20:40:12 Auckland kernel: submit_bio+0x51/0x1b0
avril 08 20:40:12 Auckland kernel: ? bio_add_page+0x6a/0x90
avril 08 20:40:12 Auckland kernel: submit_bh_wbc+0x182/0x1b0
avril 08 20:40:12 Auckland kernel: submit_bh+0x13/0x20
avril 08 20:40:12 Auckland kernel: jbd2_journal_commit_transaction+0x5d0/0x17f0
avril 08 20:40:12 Auckland kernel: kjournald2+0xb6/0x280
avril 08 20:40:12 Auckland kernel: ? wait_woken+0x80/0x80
avril 08 20:40:12 Auckland kernel: kthread+0x114/0x150
avril 08 20:40:12 Auckland kernel: ? commit_timeout+0x20/0x20
avril 08 20:40:12 Auckland kernel: ? kthread_park+0x90/0x90
avril 08 20:40:12 Auckland kernel: ret_from_fork+0x1f/0x30
avril 08 20:40:12 Auckland kernel: INFO: task kworker/u16:68:27721 blocked for more than 120 seconds.
avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu
avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
avril 08 20:40:12 Auckland kernel: kworker/u16:68 D 0 27721 2 0x00004000
avril 08 20:40:12 Auckland kernel: Workqueue: writeback wb_workfn (flush-259:0)
avril 08 20:40:12 Auckland kernel: Call Trace:
avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60
avril 08 20:40:12 Auckland kernel: ? alloc_pages_current+0x87/0xe0
avril 08 20:40:12 Auckland kernel: ? bit_wait_io_timeout+0x70/0x70
avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0
avril 08 20:40:12 Auckland kernel: io_schedule+0x16/0x40
avril 08 20:40:12 Auckland kernel: bit_wait_io+0x11/0x50
avril 08 20:40:12 Auckland kernel: __wait_on_bit+0x33/0xa0
avril 08 20:40:12 Auckland kernel: out_of_line_wait_on_bit+0x8d/0xb0
avril 08 20:40:12 Auckland kernel: ? var_wake_function+0x30/0x30
avril 08 20:40:12 Auckland kernel: do_get_write_access+0x29b/0x3c0
avril 08 20:40:12 Auckland kernel: jbd2_journal_get_write_access+0x63/0x90
avril 08 20:40:12 Auckland kernel: __ext4_journal_get_write_access+0x7a/0x120
avril 08 20:40:12 Auckland kernel: ext4_mb_mark_diskspace_used+0x80/0x430
avril 08 20:40:12 Auckland kernel: ext4_mb_new_blocks+0x291/0x610
avril 08 20:40:12 Auckland kernel: ext4_ext_map_blocks+0x867/0xde0
avril 08 20:40:12 Auckland kernel: ext4_map_blocks+0xf3/0x590
avril 08 20:40:12 Auckland kernel: ? kmem_cache_alloc+0x178/0x230
avril 08 20:40:12 Auckland kernel: ? ext4_alloc_io_end_vec+0x1e/0x50
avril 08 20:40:12 Auckland kernel: ext4_writepages+0x767/0xd60
avril 08 20:40:12 Auckland kernel: ? find_next_and_bit+0xc/0x10
avril 08 20:40:12 Auckland kernel: do_writepages+0x43/0xd0
avril 08 20:40:12 Auckland kernel: ? do_writepages+0x43/0xd0
avril 08 20:40:12 Auckland kernel: __writeback_single_inode+0x44/0x350
avril 08 20:40:12 Auckland kernel: ? free_pd+0x1b/0x20 [i915]
avril 08 20:40:12 Auckland kernel: writeback_sb_inodes+0x22d/0x4b0
avril 08 20:40:12 Auckland kernel: __writeback_inodes_wb+0x56/0xf0
avril 08 20:40:12 Auckland kernel: wb_writeback+0x20c/0x2f0
avril 08 20:40:12 Auckland kernel: ? cpumask_next+0x1b/0x20
avril 08 20:40:12 Auckland kernel: wb_workfn+0x388/0x4e0
avril 08 20:40:12 Auckland kernel: ? __switch_to+0x7f/0x450
avril 08 20:40:12 Auckland kernel: ? __switch_to_asm+0x42/0x70
avril 08 20:40:12 Auckland kernel: ? __switch_to_asm+0x36/0x70
avril 08 20:40:12 Auckland kernel: process_one_work+0x1e8/0x3b0
avril 08 20:40:12 Auckland kernel: worker_thread+0x4d/0x3f0
avril 08 20:40:12 Auckland kernel: kthread+0x114/0x150
avril 08 20:40:12 Auckland kernel: ? process_one_work+0x3b0/0x3b0
avril 08 20:40:12 Auckland kernel: ? kthread_park+0x90/0x90
avril 08 20:40:12 Auckland kernel: ret_from_fork+0x1f/0x30
avril 08 20:40:12 Auckland kernel: INFO: task Icon Buffer:28139 blocked for more than 120 seconds.
avril 08 20:40:12 Auckland kernel: Not tainted 5.8.0-48-generic #54~20.04.1-Ubuntu
avril 08 20:40:12 Auckland kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
avril 08 20:40:12 Auckland kernel: Icon Buffer D 0 28139 28126 0x00000000
avril 08 20:40:12 Auckland kernel: Call Trace:
avril 08 20:40:12 Auckland kernel: __schedule+0x394/0xa60
avril 08 20:40:12 Auckland kernel: schedule+0x55/0xc0
avril 08 20:40:12 Auckland kernel: blk_queue_enter+0x123/0x200
avril 08 20:40:12 Auckland kernel: ? wait_woken+0x80/0x80
avril 08 20:40:12 Auckland kernel: generic_make_request+0xa2/0x3b0
avril 08 20:40:12 Auckland kernel: ? __check_block_validity.constprop.0+0x46/0x90
avril 08 20:40:12 Auckland kernel: submit_bio+0x51/0x1b0
avril 08 20:40:12 Auckland kernel: ? bio_add_page+0x6a/0x90
avril 08 20:40:12 Auckland kernel: ext4_mpage_readpages+0x21b/0xa30
avril 08 20:40:12 Auckland kernel: ? __mod_lruvec_state+0x41/0xf0
avril 08 20:40:12 Auckland kernel: ext4_readahead+0x33/0x40
avril 08 20:40:12 Auckland kernel: read_pages+0x8e/0x280
avril 08 20:40:12 Auckland kernel: ? add_to_page_cache_lru+0x78/0xd0
avril 08 20:40:12 Auckland kernel: page_cache_readahead_unbounded+0x147/0x200
avril 08 20:40:12 Auckland kernel: __do_page_cache_readahead+0x35/0x40
avril 08 20:40:12 Auckland kernel: ondemand_readahead+0x148/0x2a0
avril 08 20:40:12 Auckland kernel: page_cache_sync_readahead+0x78/0xc0
avril 08 20:40:12 Auckland kernel: generic_file_buffered_read+0x598/0xc50
avril 08 20:40:12 Auckland kernel: generic_file_read_iter+0xdc/0x140
avril 08 20:40:12 Auckland kernel: ext4_file_read_iter+0x58/0x180
avril 08 20:40:12 Auckland kernel: new_sync_read+0x10c/0x1a0
avril 08 20:40:12 Auckland kernel: vfs_read+0x161/0x190
avril 08 20:40:12 Auckland kernel: ksys_read+0x67/0xe0
avril 08 20:40:12 Auckland kernel: __x64_sys_read+0x1a/0x20
avril 08 20:40:12 Auckland kernel: do_syscall_64+0x49/0xc0
avril 08 20:40:12 Auckland kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
avril 08 20:40:12 Auckland kernel: RIP: 0033:0x7f107da5583d
avril 08 20:40:12 Auckland kernel: RSP: 002b:00007f107a8f26d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
avril 08 20:40:12 Auckland kernel: RAX: ffffffffffffffda RBX: 000000000000492a RCX: 00007f107da5583d
avril 08 20:40:12 Auckland kernel: RDX: 0000000000001000 RSI: 00007f107a8f26f0 RDI: 0000000000000005
avril 08 20:40:12 Auckland kernel: RBP: 00007f107a8f26f0 R08: 0000000000000000 R09: 0000000000000010
avril 08 20:40:12 Auckland kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1068003c90
avril 08 20:40:12 Auckland kernel: R13: 00007f10680026e0 R14: 0000000000000005 R15: 00007f10680026e0
avril 08 20:41:11 Auckland kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
avril 08 20:41:11 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 1539674240 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
avril 08 20:41:11 Auckland kernel: nvme nvme0: Abort status: 0x371
avril 08 20:41:11 Auckland kernel: nvme nvme0: Abort status: 0x371
avril 08 20:41:11 Auckland kernel: nvme nvme0: Abort status: 0x371
avril 08 20:41:11 Auckland kernel: nvme nvme0: Abort status: 0x371
avril 08 20:41:11 Auckland kernel: nvme nvme0: Abort status: 0x371
avril 08 20:43:12 Auckland kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
avril 08 20:43:12 Auckland kernel: nvme nvme0: Removing after probe failure status: -19
avril 08 20:45:12 Auckland kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 973377520 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
avril 08 20:45:12 Auckland kernel: Aborting journal on device nvme0n1p1-8.
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 121667584, lost sync page write
avril 08 20:45:12 Auckland kernel: JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: Detected aborted journal
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): Remounting filesystem read-only
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 1539313512 op 0x1:(WRITE) flags 0x103000 phys_seg 17 prio class 0
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413933, lost async page write
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413934, lost async page write
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413935, lost async page write
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413936, lost async page write
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:345: I/O error 10 writing to inode 12 starting block 10106112)
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413937, lost async page write
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413938, lost async page write
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413939, lost async page write
avril 08 20:45:12 Auckland kernel: Buffer I/O error on dev nvme0n1p1, logical block 192413940, lost async page write
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 268437760 op 0x1:(WRITE) flags 0x103000 phys_seg 2 prio class 0
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 76976 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 11312 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 2056 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 80848752 op 0x1:(WRITE) flags 0x0 phys_seg 9 prio class 0
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:345: I/O error 10 writing to inode 12 starting block 10106112)
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 80848568 op 0x1:(WRITE) flags 0x4000 phys_seg 12 prio class 0
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:345: I/O error 10 writing to inode 12 starting block 10106094)
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 1568674440 op 0x1:(WRITE) flags 0x103000 phys_seg 14 prio class 0
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105335
avril 08 20:45:12 Auckland kernel: blk_update_request: I/O error, dev nvme0n1, sector 1564478208 op 0x1:(WRITE) flags 0x103000 phys_seg 29 prio class 0
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105336
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105337
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105338
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105339
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105340
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105341
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105342
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105343
avril 08 20:45:12 Auckland kernel: Buffer I/O error on device nvme0n1p1, logical block 10105344
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:345: I/O error 10 writing to inode 12 starting block 10106618)
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): ext4_check_bdev_write_error:215: comm kworker/u16:68: Error while async write back metadata
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1) in ext4_reserve_inode_write:5675: Journal has aborted
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): mpage_map_and_submit_extent:2502: inode #12: comm kworker/u16:68: mark_inode_dirty error
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): mpage_map_and_submit_extent:2504: comm kworker/u16:68: Failed to mark inode 12 dirty
avril 08 20:45:12 Auckland kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:345: I/O error 10 writing to inode 12 starting block 10107122)
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 1.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 1158.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 9366.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 33554464.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 33554465.
...
...
... There are 678 lines like this. I cut to make it readeable.
...
...
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084059.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084060.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084061.
avril 08 20:45:12 Auckland kernel: JBD2: Error while async write back metadata bh 196084062.
avril 08 20:45:12 Auckland kernel: nvme nvme0: failed to set APST feature (-19)
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool: reading directory lblock 0
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool: reading directory lblock 0
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
avril 08 20:45:12 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm gvfs-udisks2-vo: error -5 reading directory block
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool: reading directory lblock 0
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool-org.gnome.: reading directory lblock 0
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool-org.gnome.: reading directory lblock 0
avril 08 20:45:12 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm pool-org.gnome.: reading directory lblock 0
avril 08 20:45:21 Auckland kernel: EXT4-fs warning: 21 callbacks suppressed
avril 08 20:45:21 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm ls: error -5 reading directory block
avril 08 20:45:24 Auckland kernel: EXT4-fs error: 3 callbacks suppressed
avril 08 20:45:24 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm bash: reading directory lblock 0
avril 08 20:45:24 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm bash: reading directory lblock 0
avril 08 20:45:24 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #2: comm bash: reading directory lblock 0
avril 08 20:45:30 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm ls: error -5 reading directory block
avril 08 20:45:47 Auckland kernel: EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1004: inode #2: lblock 0: comm pool-org.gnome.: error -5 reading directory block
avril 08 20:46:30 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #54788097: comm codium: reading directory lblock 0
avril 08 20:46:30 Auckland kernel: EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1535: inode #54788097: comm codium: reading directory lblock 0

I think April, 8th is the last time I faced the problem.

robin@Auckland:~$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-48-generic 5.8.0-48.54~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 14 23:45:25 2021
InstallationDate: Installed on 2021-03-23 (22 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[João Pedro Seara (jpseara)]

I am observing the same in Ubuntu 22.04 @ 5.15.0-46-generic.