From: Tvrtko Ursulin <tvrtko@ursulin.net>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.33-rc2] kernel BUG at fs/ext4/inode.c:1063!
Date: Mon, 4 Jan 2010 08:14:06 +0000 [thread overview]
Message-ID: <201001040814.07013.tvrtko@ursulin.net> (raw)
In-Reply-To: <20100104010836.GA4527@thunk.org>
On Monday 04 Jan 2010 01:08:36 tytso@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
prev parent reply other threads:[~2010-01-04 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 16:38 [2.6.33-rc2] kernel BUG at fs/ext4/inode.c:1063! Tvrtko Ursulin
2010-01-04 1:08 ` tytso
2010-01-04 8:14 ` Tvrtko Ursulin [this message]
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=201001040814.07013.tvrtko@ursulin.net \
--to=tvrtko@ursulin.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).