Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S267870AbTBKOYU>; Tue, 11 Feb 2003 09:24:20 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S267876AbTBKOYU>; Tue, 11 Feb 2003 09:24:20 -0500
Received: from pc-80-195-34-144-ed.blueyonder.co.uk ([80.195.34.144]:15489
	"EHLO sisko.scot.redhat.com") by vger.kernel.org with ESMTP
	id <S267869AbTBKOYS>; Tue, 11 Feb 2003 09:24:18 -0500
Subject: Re: [Ext2-devel] Re: fsck out of memory
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Stephan van Hienen <raid@a2000.nu>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-kernel@vger.kernel.org,
       linux-raid@vger.kernel.org, ext2-devel@lists.sourceforge.net,
       "Theodore Ts'o" <tytso@mit.edu>, peter@chubb.wattle.id.au, tbm@a2000.nu,
       Stephen Tweedie <sct@redhat.com>
In-Reply-To: <Pine.LNX.4.53.0302111410350.13269@ddx.a2000.nu>
References: <Pine.LNX.4.53.0302071555110.718@ddx.a2000.nu>
	<Pine.LNX.4.53.0302071800200.1306@ddx.a2000.nu>
	<20030207102858.P18636@schatzie.adilger.int>
	<Pine.LNX.4.53.0302090953440.1039@ddx.a2000.nu>
	<1044917060.11838.108.camel@sisko.scot.redhat.com> 
	<Pine.LNX.4.53.0302111410350.13269@ddx.a2000.nu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-11james) 
Date: 11 Feb 2003 14:33:02 +0000
Message-Id: <1044973982.1980.29.camel@sisko.scot.redhat.com>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1235
Lines: 35

Hi,

On Tue, 2003-02-11 at 13:11, Stephan van Hienen wrote:
> > On Sun, 2003-02-09 at 10:08, Stephan van Hienen wrote:
> >
> > > Feb  7 04:18:15 storage kernel: EXT3-fs error (device md(9,0)):
> > > ext3_new_block:
> > > Allocating block in system zone - block = 536875638
> >
> > That looks like it could be a block wrap, amongst other possible causes.
> hmms and this means ?

One possible cause here is that some component of the system has wrapped
the block number round at 2TB, rather than correctly going beyond 2TB,
resulting in the wrong block being picked up as a bitmap block.

> > Well, that's the most likely candidate, because it's the least tested
> > component.  Are you using Ben LaHaise's LBD fixes for the md devices?
> > Without those, md and lvm are not LBD-safe.
> where can i find this lbd fixes for md ?

I've no idea.  Ben has some lb patches up at

  http://people.redhat.com/bcrl/lb/

but there's nothing broken out against the latest lbd diffs.

Cheers,
 Stephen

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