Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Apr 2002 12:29:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Apr 2002 12:29:19 -0400 Received: from flaxian.hitnet.RWTH-Aachen.DE ([137.226.181.79]:19984 "EHLO moria.gondor.com") by vger.kernel.org with ESMTP id ; Sun, 21 Apr 2002 12:29:16 -0400 Date: Sun, 21 Apr 2002 18:29:15 +0200 From: Jan Niehusmann To: linux-kernel@vger.kernel.org Subject: ext3: i_blocks is xx, should be yy Message-ID: <20020421162915.GA28414@gondor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On an (otherwise clean, and cleanly unmounted) ext3 partition, I got some ext2fs errors like the following: Inode 295208, i_blocks is 112, should be 8. Fix? Inode 295342, i_blocks is 8, should be 0. Fix? Inode 295343, i_blocks is 8, should be 0. Fix? Inode 295344, i_blocks is 8, should be 0. Fix? [...] I looked up the inodes with debug2fs and noticed that all of them belong to files which probably had failed write attemps because the fs was full. This happened with 2.4.18-rc2-ac1, neither the latest one nor a 'release' version, but I don't remember reading about such a problem on linux-kernel. Jan - 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/