From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 28 Sep 2002 10:13:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 28 Sep 2002 10:13:53 -0400 Received: from thunk.org ([140.239.227.29]:19875 "EHLO thunker.thunk.org") by vger.kernel.org with ESMTP id ; Sat, 28 Sep 2002 10:13:52 -0400 Date: Sat, 28 Sep 2002 10:18:41 -0400 From: "Theodore Ts'o" To: Ryan Cumming , Andreas Dilger , linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net Subject: Re: [BK PATCH] Add ext3 indexed directory (htree) support Message-ID: <20020928141841.GB653@think.thunk.org> Mail-Followup-To: Theodore Ts'o , Ryan Cumming , Andreas Dilger , linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net References: <20020926235741.GC10551@think.thunk.org> <20020927041234.GS22795@clusterfs.com> <200209271820.41906.ryan@completely.kicks-ass.org> <20020928141330.GA653@think.thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020928141330.GA653@think.thunk.org> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Oh, one other thing. I'm pretty sure the rest of the errors you saw were a result of the fact that you had your filesystem set to remount the filesystem read-only after running into errors. When the error was detected, all existing updates to the filesystem are aborted (to minimize damage to the filesystem), and that can leave the filesystem in a somewhat inconsistent state, although nothing which e2fsck shouldn't be able to fix. When running with the filesystem set to continue-with-errors, the only problem which e2fsck picks up is the too-small-to-be-sane directory entry problem. - Ted