Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 6 Nov 2002 03:20:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 6 Nov 2002 03:20:30 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:2263 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id ; Wed, 6 Nov 2002 03:20:30 -0500 Date: Wed, 6 Nov 2002 09:26:58 +0100 From: Jens Axboe To: Linux Kernel Cc: ext2-devel@lists.sourceforge.net Subject: Re: 2.5.46 ext3 errors Message-ID: <20021106082658.GD1137@suse.de> References: <20021106075406.GC1137@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021106075406.GC1137@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1121 Lines: 27 On Wed, Nov 06 2002, Jens Axboe wrote: > Hi, > > Doing a kernel compile, the file system suddenly turned read-only. > Following messages appeared in log: > > EXT3-fs error (device ide1(22,1)): ext3_new_inode: Free inodes count corrupted in group 688 Aborting journal on device ide1(22,1). > ext3_new_inode: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide1(22,1)) in ext3_new_inode: Journal has aborted > EXT3-fs error (device ide1(22,1)) in ext3_create: Journal has aborted ext3_abort called. > EXT3-fs abort (device ide1(22,1)): ext3_journal_start: Detected aborted journal > Remounting filesystem read-only fsck gave, for that group: Free inodes count wrong for group #688 (65534, counted=0) I've got full fsck log if anyone wants to see it, it consists of wrong inode and directory counts only. -- Jens Axboe - 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/