From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n71InJcx236572 for ; Sat, 1 Aug 2009 13:49:26 -0500 Received: from bombadil.infradead.org (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 54B4639CB60 for ; Sat, 1 Aug 2009 11:49:44 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) by cuda.sgi.com with ESMTP id 8lZzcVk6WKG5bkWg for ; Sat, 01 Aug 2009 11:49:44 -0700 (PDT) Date: Sat, 1 Aug 2009 14:49:43 -0400 From: Christoph Hellwig Subject: Re: [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock Message-ID: <20090801184943.GA2712@infradead.org> References: <4A6492AF.3030809@sandeen.net> <20090720212153.GA6832@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20090720212153.GA6832@infradead.org> 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: Eric Sandeen Cc: xfs mailing list On Mon, Jul 20, 2009 at 05:21:53PM -0400, Christoph Hellwig wrote: > On Mon, Jul 20, 2009 at 10:52:15AM -0500, Eric Sandeen wrote: > > In Red Hat Bug 512552 > > - Can't write to XFS mount during raid5 resync > > > > a user ran into corruption while resyncing a raid, and we failed > > a consistency test, but didn't get much more info; it'd be nice > > to call XFS_CORRUPTION_ERROR here so we can see the buffer > > contents. > > > > Compile-tested only... > > Looks good to me, I'll throw it into my XFSQA queue.. I has survied quite a few xfsqa runs for me, so Reviewed-by: Christoph Hellwig sounds like another 2.6.31 candidate to me.. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs