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 03:52:50 +0000 [thread overview]
Message-ID: <bug-76261-13602-QSPXKkxUGj@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 #7 from Theodore Tso <tytso@mit.edu> ---
Look, if you're complaining about long shutdown times, you can do a forced
shutdown. You will then lose data. If you care about not losing data, then
you have to wait for all of the data to be written out to flash. There's no
magic pixie dust here. You can have a clean shutdown that might take a little
while, and no data loss, or you can live with the potential risk of data loss
if you can't stand waiting even a tiny bit of time for the shutdown to finish
up.
The other question is why is some user process writing so much to the file
system before the system is shutdown. Is this really some ill-behaved user
application which is burning huge amounts of flash lifespan and battery life by
constantly writing to flash? Or is there some other bug going on which is
causing system processes to write huge amounts of logs or other junk to the
file system unnecessarily?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-16 3:52 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 [this message]
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-QSPXKkxUGj@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).