Should this go here, or the devel list?
2022-07-05T11:05:50.127140-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165908482: comm firefox: reading directory lblock 0 2022-07-05T11:05:50.127574-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_wait_block_bitmap:532: comm IndexedDB #724: Cannot read block bitmap - block_group = 9174, block_bitmap = 300417030 2022-07-05T11:05:50.152383-07:00 localhost kernel: EXT4-fs (dm-7): Delayed block allocation failed for inode 167575560 at logical offset 0 with max blocks 1 with error 5 2022-07-05T11:05:50.159591-07:00 localhost kernel: EXT4-fs (dm-7): This should not happen!! Data will be lost 2022-07-05T11:05:50.168021-07:00 localhost kernel: EXT4-fs warning (device dm-7): ext4_add_entry:2377: inode #165904385: lblock 0: comm firefox: error -5 reading directory block 2022-07-05T11:05:50.172627-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165908484: comm firefox: reading directory lblock 0 2022-07-05T11:05:50.172704-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165908482: comm firefox: reading directory lblock 0 2022-07-05T11:05:50.564696-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165617665: comm gsd-color: reading directory lblock 0 2022-07-05T11:05:50.564863-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_get_inode_loc:4576: inode #165609493: block 1324875809: comm gsd-color: unable to read itable block 2022-07-05T11:05:50.611903-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_get_inode_loc:4576: inode #165609493: block 1324875809: comm gsd-color: unable to read itable block 2022-07-05T11:05:50.627480-07:00 localhost kernel: EXT4-fs error (device dm-7) in ext4_reserve_inode_write:5748: IO failure 2022-07-05T11:05:50.641644-07:00 localhost kernel: EXT4-fs error (device dm-7) in ext4_orphan_add:188: IO failure 2022-07-05T11:05:50.655065-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_get_inode_loc:4576: inode #165609493: block 1324875809: comm gsd-color: unable to read itable block 2022-07-05T11:05:50.724704-07:00 localhost kernel: EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1044: inode #165543937: lblock 0: comm updatedb: error -5 reading directory block 2022-07-05T11:06:03.113724-07:00 localhost kernel: EXT4-fs error: 16 callbacks suppressed 2022-07-05T11:06:03.113925-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165654532: comm gnome-shell: reading directory lblock 0 2022-07-05T11:06:03.124575-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:03.124637-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm gnome-shell: Detected aborted journal 2022-07-05T11:06:03.124794-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:03.124837-07:00 localhost kernel: EXT4-fs (dm-7): Remounting filesystem read-only 2022-07-05T11:06:35.711297-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:06:35.718013-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:54.859144-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:06:54.864491-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:58.405981-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:06:58.416978-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:05.526024-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:07:05.539798-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:08.309750-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:07:08.317093-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.246700-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_wait_block_bitmap:532: comm gdbus: Cannot read block bitmap - block_group = 10030, block_bitmap = 328204302 2022-07-05T11:07:26.246844-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_discard_preallocations:5042: comm gdbus: Error -5 loading buddy information for 10030 2022-07-05T11:07:26.281601-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.281630-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_wait_block_bitmap:532: comm gdbus: Cannot read block bitmap - block_group = 110, block_bitmap = 3145742 2022-07-05T11:07:26.281673-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_discard_preallocations:5042: comm gdbus: Error -5 loading buddy information for 110 2022-07-05T11:07:26.287078-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.305711-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165732354: comm gnome-session-b: reading directory lblock 0 2022-07-05T11:07:26.315945-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165732354: comm gnome-session-b: reading directory lblock 0 2022-07-05T11:07:26.316058-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.320614-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165732354: comm gnome-session-b: reading directory lblock 0 2022-07-05T11:07:26.325084-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.325116-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock
On Tue, 5 Jul 2022 17:38:56 -0700 Joseph D Wagner joe@josephdwagner.info wrote:
Should this go here, or the devel list?
This looks like a failing drive. You could try umounting the drive from a rescue boot, and then running e2fsck on the partition, e2fsck /dev/sd[a,b,etc.][1,2,etc.] or smartctl -a /dev/sd[a,b,etc.] to see if it can be recovered, and what its error status is.
[snipped error messages]
On Tue, Jul 5, 2022 at 8:40 PM Joseph D Wagner joe@josephdwagner.info wrote:
Should this go here, or the devel list?
Is this filtered in any way? Can you post a complete dmesg?