From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id n0AGRZss003096 for ; Sat, 10 Jan 2009 10:27:35 -0600 Message-ID: <4968CC73.4070700@sandeen.net> Date: Sat, 10 Jan 2009 10:27:31 -0600 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: [xfs-masters] 2.6.29-rc: kernel BUG at fs/xfs/support/debug.c:108 References: <20090109044121.GA31280@orion> <20090109053858.GP9448@disturbed> <20090110143924.GA25900@infradead.org> In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Alexander Beregalov Cc: Christoph Hellwig , xfs-masters@oss.sgi.com, kernel-testers@vger.kernel.org, xfs@oss.sgi.com Alexander Beregalov wrote: > 2009/1/10 Christoph Hellwig : >> How big is the filesystem where you see this corruption? Maybe I could >> reproduce it locally with a xfs_metadump image. > > They are big enough, I have four such FS's for >200Gb An xfs_metadump should not be so large, though. But bisecting as hch suggested (keepin the "working" header for each bisection point) would be great. -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs