From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12543] ext4_da_writepages error in 2.6.28.1 after a disk error
Date: Tue, 27 Jan 2009 11:08:13 -0800 (PST) [thread overview]
Message-ID: <20090127190813.6E77B108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12543-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12543
tytso@mit.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |PATCH_ALREADY_AVAILABLE
------- Comment #3 from tytso@mit.edu 2009-01-27 11:08 -------
Having ext4 handling this gracefully is already in mainline. See commit:
2a21e37e4: ext4: tone down ext4_da_writepages warnings
ext4: tone down ext4_da_writepages warnings
If the filesystem has errors, ext4_da_writepages() will return a *lot*
of errors, including lots and lots of stack dumps. While it's true
that we are dropping user data on the floor, which is unfortunate, the
stack dumps aren't helpful, and they tend to obscure the true original
root cause of the problem. So in the case where the filesystem has
aborted, return an EROFS right away.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
It is in 2.6.29-rc1 and I plan to send it for the 2.6.28.y release, just
because it is *so* annoying.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2009-01-27 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 16:56 [Bug 12543] New: ext4_da_writepages error in 2.6.28.1 after a disk error bugme-daemon
2009-01-27 18:19 ` [Bug 12543] " bugme-daemon
2009-01-27 18:26 ` bugme-daemon
2009-01-27 19:08 ` bugme-daemon [this message]
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=20090127190813.6E77B108040@picon.linux-foundation.org \
--to=bugme-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).