From: Chris Kottaridis Subject: new_block error Date: Thu, 28 Feb 2008 11:45:50 -0700 Message-ID: <1204224350.16889.30.camel@worker.quietwind.net> Reply-To: chriskot@quietwind.net Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit To: linux-fsdevel@vger.kernel.org Return-path: Received: from servy.quietwind.net ([71.39.149.33]:59921 "EHLO servy.quietwind.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757683AbYB1TLV (ORCPT ); Thu, 28 Feb 2008 14:11:21 -0500 Received: from [192.65.171.33] (worker.quietwind.net [192.65.171.33]) by servy.quietwind.net (8.13.1/8.13.1) with ESMTP id m1SIkj46036910 for ; Thu, 28 Feb 2008 11:46:45 -0700 (MST) (envelope-from chriskot@quietwind.net) Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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. Any comments appreciated. Thanks Chris Kottaridis (chriskot@quietwind.net)