From: Theodore Tso <tytso@mit.edu>
To: "Jörg Sommer" <joerg@alea.gnuu.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 fails on ext2 filesystems
Date: Tue, 20 Jan 2009 09:51:00 -0500 [thread overview]
Message-ID: <20090120145100.GD10037@mit.edu> (raw)
In-Reply-To: <20090118100458.GA22064@alea.gnuu.de>
On Sun, Jan 18, 2009 at 11:04:59AM +0100, Jörg Sommer wrote:
> > > [ 203.082300] EXT4 FS on hda3, no journal
> > > [ 205.746713] EXT4-fs error (device hda3): ext4_free_data: circular indirect block detected, inode=165056, block=184476
> > >
Hi, this patch should fix your problem.
- Ted
commit bf3baec2b4529dcf47ee422a48b8c0e83df7f0a0
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Jan 20 09:50:19 2009 -0500
ext4: Fix ext4_free_blocks() w/o a journal when files have indirect blocks
When trying to unlink a file with indirect blocks on a filesystem
without a journal, the "circular indirect block" sanity test was
getting falsely triggered.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 49484ba..b4386da 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -3622,7 +3622,7 @@ static void ext4_free_data(handle_t *handle, struct inode *inode,
* block pointed to itself, it would have been detached when
* the block was cleared. Check for this instead of OOPSing.
*/
- if (bh2jh(this_bh))
+ if ((EXT4_JOURNAL(inode) == NULL) || bh2jh(this_bh))
ext4_handle_dirty_metadata(handle, inode, this_bh);
else
ext4_error(inode->i_sb, __func__,
--
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
next prev parent reply other threads:[~2009-01-20 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 1:35 ext4 fails on ext2 filesystems Jörg Sommer
2009-01-18 2:38 ` Theodore Tso
2009-01-18 10:04 ` Jörg Sommer
2009-01-20 14:51 ` Theodore Tso [this message]
2009-01-21 18:45 ` Jörg Sommer
2009-01-21 19:58 ` Theodore Tso
2009-01-19 23:30 ` Andreas Dilger
2009-01-20 13:56 ` Jörg Sommer
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=20090120145100.GD10037@mit.edu \
--to=tytso@mit.edu \
--cc=joerg@alea.gnuu.de \
--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).