From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 76261] ext4_da_writepages err -30 after remount ro during shutdown
Date: Fri, 16 May 2014 04:27:15 +0000 [thread overview]
Message-ID: <bug-76261-13602-aOZ5bnX1dX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-76261-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=76261
--- Comment #8 from kun.chen <kun.chen@mediatek.com> ---
Sorry, I'm not say clear.
Ext4 was mounted as dealloc, when applications write, they don't know shutdown
happened later. So after emergency remount ro, flush worker begin write dirty
data. This flow maybe normal. But as system already remounted to read only,
whether we want or not, already can't flush dirty data back, so still writeback
seems unnecessary.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-16 4:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 5:01 [Bug 76261] New: ext4_da_writepages err -30 after remount ro during shutdown bugzilla-daemon
2014-05-15 15:11 ` [Bug 76261] " 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 [this message]
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-aOZ5bnX1dX@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).