From: Mark Lord <lkml@rtr.ca>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3: Freeing blocks not in datazone
Date: Mon, 14 Apr 2008 19:09:16 -0400 [thread overview]
Message-ID: <4803E41C.1080003@rtr.ca> (raw)
In-Reply-To: <4803C5E4.3030804@redhat.com>
Eric Sandeen wrote:
> Mark Lord wrote:
>> Eric Sandeen wrote:
>>> Mark Lord wrote:
>>>> One of my test systems here, running 2.6.25-rc8-git*,
>>>> just now crapped out with this in the tail end of dmesg:
>>>>
>>>> [ 20.927780] EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks not in datazone - block
>>>> [ 20.928756] Aborting journal on device sda1.
>>> I've got a similar report from the F9 installer, also on 2.6.25-rc8* ...
>>> trying to reproduce locally.
>> ..
>>
>> Well, if it's of any help, here it was on a 2.4GHz Intel QuadCore,
>> 32-bit kernel/userspace, 4GB RAM, PAE-enabled.
>
> Any chance you had done a resize2fs, online or offline, before this?
> Just a guess based on the installer thing I'm looking at...
..
No, nothing really special there.
It's just a single drive / single filesystem (K)Ubuntu install originally,
with various test 2.6.25-rc* kernels being substituted in.
There are lots of other drives in the box for driver development,
but they have nothing to do with the ext3 root fs.
My guess would be that the 4 fast CPU cores managed to race on something.
Cheers
next prev parent reply other threads:[~2008-04-14 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 18:23 ext3: Freeing blocks not in datazone Mark Lord
2008-04-14 19:23 ` Eric Sandeen
2008-04-14 20:32 ` Mark Lord
2008-04-14 21:00 ` Eric Sandeen
2008-04-14 23:09 ` Mark Lord [this message]
2008-04-22 9:31 ` Jan Kara
2008-04-22 13:41 ` Eric Sandeen
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=4803E41C.1080003@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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