Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422832AbWBIGyb (ORCPT ); Thu, 9 Feb 2006 01:54:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422834AbWBIGya (ORCPT ); Thu, 9 Feb 2006 01:54:30 -0500 Received: from smtp.osdl.org ([65.172.181.4]:50561 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1422832AbWBIGya (ORCPT ); Thu, 9 Feb 2006 01:54:30 -0500 Date: Wed, 8 Feb 2006 22:53:59 -0800 From: Andrew Morton To: Helge Hafting Cc: linux-kernel@vger.kernel.org, Mingming Cao Subject: Re: fsck: i_blocks is xxx should be yyy on ext3 Message-Id: <20060208225359.426573cf.akpm@osdl.org> In-Reply-To: <43EA079A.4010108@aitel.hist.no> References: <43EA079A.4010108@aitel.hist.no> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 787 Lines: 27 Helge Hafting wrote: > > Today I rebooted into 2.6.16-rc2-mm1. Fsck checked a "clean" ext3 fs, > because it was many mounts since the last time. > > I have seen that many times, but this time I got a lot of > "i_blocks is xxx, should be yyy fix?" > > In all cases, the blocks were fixed to a lower number. Yes, thanks. It's due to the ext3_getblocks() patches in -mm. I can't think of any actual harm which it'll cause. To reproduce: mkfs mount dbench 32 killall dbench umount fsck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/