To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.69] ext3 error: rec_len %% 4 != 0
References: <8765nva43w.fsf@deneb.enyo.de>
	<20030528012512.5d631827.akpm@digeo.com>
From: Florian Weimer <fw@deneb.enyo.de>
Mail-Followup-To: Andrew Morton <akpm@digeo.com>,
 linux-kernel@vger.kernel.org
Date: Wed, 28 May 2003 10:50:44 +0200
In-Reply-To: <20030528012512.5d631827.akpm@digeo.com> (Andrew Morton's
 message of "Wed, 28 May 2003 01:25:12 -0700")
Message-ID: <87ptm38nff.fsf@deneb.enyo.de>
User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 982
Lines: 31

Andrew Morton <akpm@digeo.com> writes:

> Are you using htree?  Run
>
> 	dumpe2fs -h /dev/hda1 | grep features
>
> and if it says "dir_index" then try turning it off:
>
> 	tune2fs -O ^dir_index /dev/hda1
>
> and reboot.

No dir_index here, sorry.

> If it is not an htree problem (and htree seems pretty stable now)
> then possibly the IO system has lost some data.  If possible, try
> using a normal old disk (no RAID).

Sorry, that's not possible, the data does not fit onto a single
disk. 8-(

> Falling back to ext2 for a while would be interesting.

Okay, will fallback to ext2 next time a reboot is required.  (I guess
removing the has_journal feature using tune2fs is the easiest way to
do this, after a clean unmount, of course.)
-
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/