Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40371 - ext4_da_writepages err -30 after remount ro during shutdown

Attached to Project: Arch Linux
Opened by kun chen (kun.chen) - Thursday, 15 May 2014, 05:14 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 15 May 2014, 07:41 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have a device formatted with ext4 (no_auto_da_alloc,data=ordered).

During shutdown, when I try to force remount as read-only as: sync;echo "u" > /proc/sysrq-trigger

I see these ext4 errors after remount
76.209728 Emergency Remount R/O
76.282979 Emergency Remount Complete
77.188953 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 8192 pages, ino 131067; err -30
77.205402 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 8192 pages, ino 131067; err -30
78.220353 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 8192 pages, ino 131067; err -30
79.246658 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 8192 pages, ino 131067; err -30
80.261003 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 8192 pages, ino 131067; err -30
80.272068 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 1024 pages, ino 131067; err -30
81.300966 EXT4-fs (mmcblk0p15): ext4_da_writepages: jbd2_start: 8192 pages, ino 131067; err -30
(err 30 is -EROFS, error due to writeback to read-only filesystem).

As part of remount, I think linux will writeback all drity datas. Should no writeback occur after remount R/O. Not sure why I see these errors.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 15 May 2014, 07:41 GMT
Reason for closing:  Upstream
Comment by kun chen (kun.chen) - Thursday, 15 May 2014, 05:15 GMT
my kernel version is 3.10.20
Comment by Jan de Groot (JGC) - Thursday, 15 May 2014, 05:41 GMT
Update your kernel, you're 20 versions behind what's supported.
Comment by kun chen (kun.chen) - Thursday, 15 May 2014, 06:44 GMT
We need to do develop based on 3.10.20. Does this is a known issue for 3.10.20? Has patch can fix this?

Thanks
Comment by Tobias Powalowski (tpowa) - Thursday, 15 May 2014, 07:41 GMT
This is the wrong place for this bug, please contact upstream developers.

Loading...