All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: "615998@bugs.debian.org" <615998@bugs.debian.org>,
	"Livingston, John A" <john.a.livingston@boeing.com>,
	"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: Mon, 4 Apr 2011 09:24:28 -0500	[thread overview]
Message-ID: <15E8241A-37A0-4438-849E-A157A376C7F1@boeing.com> (raw)
In-Reply-To: <20110403020227.GA19963@thunk.org>

On Apr 02, 2011, at 22:02, Ted Ts'o wrote:
> Sorry for not following up sooner.  Are you still able to reproduce
> this failure?  If I set up an identical Debian stable instance on
> EC-2, am I likely to reproduce it myself?  Do you have a package list
> or EC2 base image I can use as a starting point?

I'll need to check on this.

Unfortunately it was not a trivial process to install Debian "squeeze" onto an EC2 instance; it took a couple ugly Perl scripts, a patched Debian-Installer, and several manual post-install-but-before-reboot steps (like fixing up GRUB 0.99).  One of these days I may get time to update all that to the official "wheezy" release and submit bug reports.

I have an exact image of the failing instance, but it has proprietary data on it and if I stand up an old copy I need to be careful not to actually let it send all the queued emails :-D.

It's probably easier for me to halt email delivery and clone the working instance and try to reproduce from there.  If I recall, the (easily undone) workaround was to remount from "data=journal" to "data=ordered" on a couple filesystems.  It may take a day or two to get this done, though.

If it comes down to it I also have a base image (from "squeeze" as of 9 months ago) that could be made public after updating with new SSH keys.

Thanks again!

Cheers,
Kyle Moffett

  reply	other threads:[~2011-04-04 15:04 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 [this message]
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
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=15E8241A-37A0-4438-849E-A157A376C7F1@boeing.com \
    --to=kyle.d.moffett@boeing.com \
    --cc=615998@bugs.debian.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=john.a.livingston@boeing.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sachinp@in.ibm.com \
    --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 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.