From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 76261] New: ext4_da_writepages err -30 after remount ro during shutdown
Date: Thu, 15 May 2014 05:01:50 +0000 [thread overview]
Message-ID: <bug-76261-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=76261
Bug ID: 76261
Summary: ext4_da_writepages err -30 after remount ro during
shutdown
Product: File System
Version: 2.5
Kernel Version: 3.10.20
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: kun.chen@mediatek.com
Regression: No
Our android 4.4.2 based on linux 3.10.20
when shutdown, it will call sync, echo "u" > /proc/sysrq-trigger. But I find a
problem that sometime shutdown will hang and sometimes shutdown need long
times.
Check the kmsg log there are ext4 error occur, such as:
[76.209728]-(3)[1:init]SysRq: -(3)[1:init]Emergency Remount R/O
[76.282979] (3)[21:kworker/3:0]Emergency Remount Complete
[77.188953] (0)[84:kworker/u8:1]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
[77.205402] (0)[84:kworker/u8:1]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
[78.220353] (3)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
[79.246658] (1)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
[80.261003] (3)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
[80.272068] (3)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 1024 pages, ino 131067; err -30
[81.300966] (1)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
[81.688616] (0)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 8192 pages, ino 131067; err -30
......
[90.601634] (0)[3075:kworker/u8:5]EXT4-fs (mmcblk0p15): ext4_da_writepages:
jbd2_start: 1024 pages, ino 131067; err -30
[91.642286] (0)[3075:kworker/u8:5]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.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-05-15 5:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 5:01 bugzilla-daemon [this message]
2014-05-15 15:11 ` [Bug 76261] ext4_da_writepages err -30 after remount ro during shutdown bugzilla-daemon
2014-05-16 1:50 ` bugzilla-daemon
2014-05-16 3:32 ` bugzilla-daemon
2014-05-16 3:36 ` bugzilla-daemon
2014-05-16 3:47 ` bugzilla-daemon
2014-05-16 3:49 ` bugzilla-daemon
2014-05-16 3:52 ` bugzilla-daemon
2014-05-16 4:27 ` bugzilla-daemon
2014-05-16 5:10 ` bugzilla-daemon
2014-05-16 12:11 ` bugzilla-daemon
2014-05-16 13:44 ` bugzilla-daemon
2014-05-19 3:41 ` bugzilla-daemon
2014-05-19 12:46 ` bugzilla-daemon
2014-05-19 13:41 ` bugzilla-daemon
2016-08-03 2:10 ` bugzilla-daemon
2016-08-03 2:34 ` bugzilla-daemon
2016-08-03 2:39 ` bugzilla-daemon
2016-08-03 3:14 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-76261-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.