From: Mingming Cao Subject: Re: new_block error Date: Thu, 28 Feb 2008 14:22:59 -0800 Message-ID: <1204237379.3609.7.camel@localhost.localdomain> References: <1204224350.16889.30.camel@worker.quietwind.net> Reply-To: cmm@us.ibm.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: chriskot@quietwind.net Return-path: Received: from e2.ny.us.ibm.com ([32.97.182.142]:36192 "EHLO e2.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751148AbYB1WYe (ORCPT ); Thu, 28 Feb 2008 17:24:34 -0500 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id m1SMOJC3023614 for ; Thu, 28 Feb 2008 17:24:19 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m1SMOJEj247246 for ; Thu, 28 Feb 2008 17:24:19 -0500 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m1SMOIVu017963 for ; Thu, 28 Feb 2008 17:24:18 -0500 In-Reply-To: <1204224350.16889.30.camel@worker.quietwind.net> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, 2008-02-28 at 11:45 -0700, Chris Kottaridis wrote: > I have a 2.6.21 kernel and under heavy load I seem to be trapsing > through this code in > > fs/ext3/balloc.c ext3_new_blocks(): > > if (in_range(le32_to_cpu(gdp->bg_block_bitmap), ret_block, num) || > in_range(le32_to_cpu(gdp->bg_inode_bitmap), ret_block, num) || > in_range(ret_block, le32_to_cpu(gdp->bg_inode_table), > EXT3_SB(sb)->s_itb_per_group) || > in_range(ret_block + num - 1, le32_to_cpu(gdp->bg_inode_table), > EXT3_SB(sb)->s_itb_per_group)) > ext3_error(sb, "ext3_new_block", > "Allocating block in system zone - " > "blocks from "E3FSBLK", length %lu", > ret_block, num); > > performed_allocation = 1; > > I get this error: > > Feb 12 13:29:24 slot0_10 kernel: EXT3-fs error (device dm-0): > ext3_new_block: Allocating block in system zone - blocks > from 86966272, length 5 > Feb 12 13:29:24 slot0_10 kernel: Aborting journal on device dm-0. > Feb 12 13:29:24 slot0_10 kernel: EXT3-fs error (device dm-0) in > ext3_reserve_inode_write: Journal has aborted > > The call to ext3_error() not only prints the error message, but calls > ext3_handle_error() which apparently puts the file system into read-only > mode. Usually the filesystem needs to be rebuilt once this happens. > > I am not real sure what the "system zone" is about here or what the > message is trying to tell us.This doesn't seem to be a out of disk space > error as there is a -ENOSPC error check earlier that we seem to get > past. It seems like the blocks were able to be allocated, so I am a > little curious about why the file system gets marked as read-only. > It complains that the new allocated block is located in the range that is used to store fs metadata (superblocks, bitmaps, inode table etc). Those fs metadata blocks should always marked as used on bitmaps, so block allocator should never returns a new block in that range if it does things correct. > Any comments appreciated. > Is there any other error message print in dmesg before the fs starts to complain? Mingming