Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: [2.6.33-rc2] kernel BUG at fs/ext4/inode.c:1063!

0 views
Skip to first unread message

ty...@mit.edu

unread,
Jan 3, 2010, 10:20:02 PM1/3/10
to
On Sun, Jan 03, 2010 at 04:38:57PM +0000, Tvrtko Ursulin wrote:
>
> As much as it was visible, all writeout stopped after this happened so I could
> only capture it with the camera. Please see the attachment.

This is a known bug. The the latest mainline version of Linux (I
think 2.6.33-rc2-git4 includes the necessary patch) will no longer
BUG. There are two more patches which I'm about to push to Linus that
are necessary to fix up a typo and some potential undesirable side
effects of the initial fix of the problem. If you want to get all of
the fixes, pull in the changes from:

git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus

Regards,

- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Tvrtko Ursulin

unread,
Jan 4, 2010, 3:20:02 AM1/4/10
to
On Monday 04 Jan 2010 01:08:36 ty...@mit.edu wrote:
> On Sun, Jan 03, 2010 at 04:38:57PM +0000, Tvrtko Ursulin wrote:
> > As much as it was visible, all writeout stopped after this happened so I
> > could only capture it with the camera. Please see the attachment.
>
> This is a known bug. The the latest mainline version of Linux (I
> think 2.6.33-rc2-git4 includes the necessary patch) will no longer
> BUG. There are two more patches which I'm about to push to Linus that
> are necessary to fix up a typo and some potential undesirable side
> effects of the initial fix of the problem. If you want to get all of
> the fixes, pull in the changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> for_linus

Was it triggered by no free space? Later I realised that may be what happened
when this triggered. I was writing out a large file which may filled the
filesystem. After reboot file in question had zero size, due to journal replay I
think, but given the amount of free space on the filesystem I think it might
have used all space while writing out.

If this is related I will wait for -rc3 and just make sure I don't run out of
space. :) (So far I avoided starting to build git trees etc)

Tvrtko

0 new messages