Messages in this thread | | | Date | Wed, 31 Aug 2022 09:55:56 +0200 | Subject | Re: ext2/zram issue [was: Linux 5.19] | From | Jiri Slaby <> |
| |
On 30. 08. 22, 23:46, charlie39@cock.li wrote: > Hi, I think i bumped on the same issue on version 5.19.2 with ext4 on zram mounted on /tmp
Only 5.19.6 contains the fix.
> ``` > # sudo dmesg -T | grep ext4 > > [Tue Aug 30 21:41:45 2022] EXT4-fs error (device zram1): ext4_check_bdev_write_error:218: comm kworker/u8:3: Error while > [Tue Aug 30 21:41:45 2022] EXT4-fs warning (device zram1): ext4_end_bio:347: I/O error 10 writing to inode 76 starting b > [Tue Aug 30 21:41:45 2022] EXT4-fs warning (device zram1): ext4_end_bio:347: I/O error 10 writing to inode 76 starting b > [Tue Aug 30 21:41:45 2022] EXT4-fs warning (device zram1): ext4_end_bio:347: I/O error 10 writing to inode 66 starting b > [Tue Aug 30 22:07:02 2022] EXT4-fs error (device zram1): ext4_journal_check_start:83: comm ThreadPoolForeg: Detected abo > [Tue Aug 30 22:07:02 2022] EXT4-fs (zram1): Remounting filesystem read-only > > ``` > Not sure what caused it, i was just updating my arch system. >
-- js
| |