From: Ted Ts'o <tytso@mit.edu>
To: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
Cc: "615998@bugs.debian.org" <615998@bugs.debian.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Sachin Sant <sachinp@in.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4
Date: Tue, 5 Apr 2011 15:07:38 -0400 [thread overview]
Message-ID: <20110405190738.GF2832@thunk.org> (raw)
In-Reply-To: <8658F8EE-A52D-4405-A1F3-C0247AB3EA6D@boeing.com>
On Tue, Apr 05, 2011 at 10:30:11AM -0500, Moffett, Kyle D wrote:
> > Couple of questions which might give me some clues:
> > (a) was this a natively formatted ext4 file system, or a ext3 file
> > system which was later converted to ext4?
>
> All the filesystems were formatted like this using Debian e2fstools
> as of 9 months ago:
Rats. OK, so the indirect block journal credit bug fix won't help
this bug.
> mke2fs -t ext4 -E lazy_itable_init=1 -L db:mail /dev/mapper/db-mail
> tune2fs -i 0 -c 1 -e remount-ro -o acl,user_xattr,journal_data /dev/mapper/db-mail
>
> Ooooh.... could the lazy_itable_init have anything to do with it?
Shouldn't be, since 2.6.32 doesn't have the lazy inode init support.
That support didn't show up until 2.6.37.
> I've switched the relevant filesystems back to data=journal mode,
> so if you want to send me a patch for 2.6.32 that I can apply to a
> Debian kernel I will keep that kernel around and if I see it happen
> again I'll check if the patch fixes it.
Given that this was a freshly created file system with mke2fs -t ext4,
I doubt the patch would help.
> Well, the base image is essentially a somewhat basic Debian "squeeze"
> for EC2 with our SSH public keys and a couple generic customizations
> applied. It does not have Postfix installed or configured, so there
> would be some work involved.
Well, if you can share that image in AWS with the ssh keys stripped
out it would save me a bunch of time. I assume it's not setup to
automatically set ssh keys and pass them back to AWS like the generic
images can?
> I also didn't see any problems with the system at all until the
> queue got backed up with ~100-120 stuck emails. After Postfix tried
> and failed to deliver a bunch of emails I would get the OOPS.
Yeah, what I'd probably try to do is install postfix and then send a
few hundred messages to foobar@example.com and see if I can repro the OOPS.
Thanks for investigating!
- Ted
next prev parent reply other threads:[~2011-04-05 19:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110301165239.3310.43806.reportbug@support.exmeritus.com>
[not found] ` <BE4E C1DF-4DFC-4B94-923D-0197B16BD7B4@boeing.com>
2011-03-01 19:26 ` Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4 Moffett, Kyle D
2011-04-03 2:02 ` Ted Ts'o
2011-04-04 14:24 ` Moffett, Kyle D
2011-04-04 20:51 ` Moffett, Kyle D
2011-04-05 0:15 ` Ted Ts'o
2011-04-05 15:30 ` Moffett, Kyle D
2011-04-05 19:07 ` Ted Ts'o [this message]
2011-04-05 19:44 ` Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernelBUG " Moffett, Kyle D
[not found] ` <20110405230538.GH2832@thunk.org>
[not found] ` <FD93E462-D97B-411B-BF09-9A64670AC5C2@boeing.com>
2011-06-23 18:32 ` Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG " Moffett, Kyle D
2011-06-23 20:55 ` Sean Ryle
2011-06-23 21:19 ` Moffett, Kyle D
2011-06-24 13:46 ` Jan Kara
2011-06-24 16:03 ` Moffett, Kyle D
2011-06-24 20:02 ` Jan Kara
2011-06-24 20:51 ` Kyle Moffett
2011-08-26 21:03 ` Moffett, Kyle D
2011-08-30 22:12 ` Jan Kara
2011-08-31 0:26 ` Moffett, Kyle D
2011-09-01 15:17 ` Jan Kara
2011-12-06 21:26 ` Moffett, Kyle D
2011-06-27 11:16 ` Lukas Czerner
2011-06-27 11:57 ` Amir Goldstein
2011-06-27 14:02 ` Jan Kara
2011-06-27 15:30 ` Lukas Czerner
2011-06-27 16:01 ` Ted Ts'o
2011-06-27 20:27 ` Jan Kara
2011-06-28 4:21 ` Moffett, Kyle D
2011-06-28 9:36 ` Jan Kara
2011-06-28 13:58 ` Ben Hutchings
2011-06-28 14:16 ` Ted Ts'o
2011-06-28 19:36 ` Moffett, Kyle D
2011-06-28 19:30 ` Moffett, Kyle D
2011-06-28 22:57 ` Jan Kara
2011-06-29 4:22 ` Moffett, Kyle D
2011-06-23 22:23 ` Ted Ts'o
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=20110405190738.GF2832@thunk.org \
--to=tytso@mit.edu \
--cc=615998@bugs.debian.org \
--cc=Kyle.D.Moffett@boeing.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sachinp@in.ibm.com \
/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).