From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ext4: call ext4_error_inode() if jbd2_journal_dirty_metadata() fails
Date: Mon, 2 Dec 2013 16:30:50 +0100 [thread overview]
Message-ID: <20131202153050.GA11721@quack.suse.cz> (raw)
In-Reply-To: <1385995502-8344-1-git-send-email-tytso@mit.edu>
On Mon 02-12-13 09:45:01, Ted Tso wrote:
> While it's true that errors can only happen if there is a bug in
> jbd2_journal_dirty_metadata(), if a bug does happen, we need to halt
> the kernel or remount the file system read-only in order to avoid
> further data loss. The ext4_journal_abort_handle() function doesn't
> do any of this, and while it's likely that this call (since it doesn't
> adjust refcounts) will likely result in the file system eventually
> deadlocking since the current transaction will never be able to close,
> it's much cleaner to call let ext4's error handling system deal with
> this situation.
>
> There's a separate bug here which is that if certain jbd2 errors
> errors occur and file system is mounted errors=continue, the file
> system will probably eventually end grind to a halt as described
> above. But things have been this way in a long time, and usually when
> we have these sorts of errors it's pretty much a disaster --- and
> that's why the jbd2 layer aggressively retries memory allocations,
> which is the most likely cause of these jbd2 errors.
>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> Cc: stable@vger.kernel.org
The patch looks good. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/ext4_jbd2.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/fs/ext4/ext4_jbd2.c b/fs/ext4/ext4_jbd2.c
> index 17ac112..3fe29de 100644
> --- a/fs/ext4/ext4_jbd2.c
> +++ b/fs/ext4/ext4_jbd2.c
> @@ -259,6 +259,15 @@ int __ext4_handle_dirty_metadata(const char *where, unsigned int line,
> if (WARN_ON_ONCE(err)) {
> ext4_journal_abort_handle(where, line, __func__, bh,
> handle, err);
> + ext4_error_inode(inode, where, line,
> + bh->b_blocknr,
> + "journal_dirty_metadata failed: "
> + "handle type %u started at line %u, "
> + "credits %u/%u, errcode %d",
> + handle->h_type,
> + handle->h_line_no,
> + handle->h_requested_credits,
> + handle->h_buffer_credits, err);
> }
> } else {
> if (inode)
> --
> 1.8.5.rc3.362.gdf10213
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2013-12-02 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 14:45 [PATCH 1/2] ext4: call ext4_error_inode() if jbd2_journal_dirty_metadata() fails Theodore Ts'o
2013-12-02 14:45 ` [PATCH 2/2] jbd2: return ENOSPC in journal_dirty_metadata if a handle runs out of space Theodore Ts'o
2013-12-02 15:35 ` Jan Kara
2013-12-03 7:34 ` Joel Becker
2013-12-02 15:30 ` Jan Kara [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=20131202153050.GA11721@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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).