Date: Wed, 28 May 2003 01:25:12 -0700
From: Andrew Morton <akpm@digeo.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.69] ext3 error: rec_len %% 4 != 0
Message-Id: <20030528012512.5d631827.akpm@digeo.com>
In-Reply-To: <8765nva43w.fsf@deneb.enyo.de>
References: <8765nva43w.fsf@deneb.enyo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 30

Florian Weimer <fw@deneb.enyo.de> wrote:
>
> Sometimes, our 2.5 test machine (actually, it's a production machine,
> please don't ask why we can't use 2.4 *sigh*) stops with an ext3 error
> message.  We have now activated proper logging, and that's what we
> got:
> 
> May 28 03:23:00 kernel: EXT3-fs error (device md0): ext3_readdir: bad entry in directory #16056745: rec_len %% 4 != 0 - offset=52, inode=431743, rec_len=37017, name_len=41 

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.

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).

Falling back to ext2 for a while would be interesting.

-
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/