Re: [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check

To:	Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject:	Re: [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock
From:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:	Sat, 1 Aug 2009 14:49:43 -0400
Cc:	xfs mailing list <xfs@xxxxxxxxxxx>
In-reply-to:	<20090720212153.GA6832@xxxxxxxxxxxxx>
References:	<4A6492AF.3030809@xxxxxxxxxxx> <20090720212153.GA6832@xxxxxxxxxxxxx>
User-agent:	Mutt/1.5.18 (2008-05-17)

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 <hch@xxxxxx>

sounds like another 2.6.31 candidate to me..

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock, Christoph Hellwig <=

Next by Date:	[PATCH] xfs: fix locking in xfs_iget_cache_hit, Christoph Hellwig
Next by Thread:	[PATCH] xfs: fix locking in xfs_iget_cache_hit, Christoph Hellwig
Indexes:	[Date] [Thread] [Top] [All Lists]

Re: [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock