Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4
On Aug 30, 2011, at 18:12, Jan Kara wrote:
> On Fri 26-08-11 16:03:32, Moffett, Kyle D wrote:
>> Ping?
>>
>> Any more ideas for debugging this issue?
>
> Sorry for not getting to you earlier.
That's ok, I have a workaround so it's been on my back burner for a while.
>> I can still trigger it on my VM snapshot very easily, so if you have anything
>> you think I should test I would be very happy to give it a shot.
>
> OK, so in the meantime I found a bug in data=journal code which could be
> related to your problem. It is fixed by commit
> 2d859db3e4a82a365572592d57624a5f996ed0ec which is in 3.1-rc1. Have you
> tried that or newer kernel as well?
>
> If the problem still is not fixed, I can provide some debugging patch to
> you. We spoke with Josef Bacik how errors like yours could happen so I have
> some places to watch...
I have not tried anything more recent; I'm actually a bit reluctant to move
away from the Debian squeeze official kernels since I do need the security
updates.
I took a quick look and I can't find that function in 2.6.32, so I assume it
would be a rather nontrivial back-port. It looks like the relevant code
used to be in ext4_clear_inode somewhere?
Out of curiosity, what would happen in data=journal mode if you unlinked a
file which still had buffers pending? That case does not seem to be handled
by that commit you mentioned, was it already handled elsewhere?
Thanks again!
Cheers,
Kyle Moffett
Reply to: