From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Something wrong with extent-based journal creation
Date: Tue, 16 Jun 2009 17:38:00 -0500 [thread overview]
Message-ID: <4A381EC8.4010202@redhat.com> (raw)
I've been tearing my hair out all day on this and not getting anywhere
yet, so punting to the list ;)
I have a user running mke2fs -t ext4 in a virt guest, and a mount
immediately after that fails.
It fails because the journal inode has an invalide i_extra_isize.
I've narrowed it down to the commit (961306d3) which creates the journal
with extent format; if that's commented out, it works fine.
I can't for the life of me see where the problem is coming from, though.
I thought we'd need a write_inode_new (emphasis on new here) for the
journal inode, but switching to that doesn't help.
I can't reproduce this myself... any ideas or suggestions of where to
look? :)
-Eric
next reply other threads:[~2009-06-16 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 22:38 Eric Sandeen [this message]
2009-06-17 0:57 ` [PATCH] libext2fs: write only core inode in update_path() Eric Sandeen
2009-06-17 15:35 ` Theodore Tso
2009-06-17 15:50 ` Eric Sandeen
2009-06-17 22:50 ` Theodore Tso
2009-06-17 23:00 ` Eric Sandeen
2009-06-17 8:04 ` Something wrong with extent-based journal creation Andreas Dilger
2009-06-17 14:45 ` Eric Sandeen
2009-06-17 15:31 ` Theodore Tso
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=4A381EC8.4010202@redhat.com \
--to=sandeen@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.