All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock
Date: Mon, 20 Jul 2009 17:21:53 -0400	[thread overview]
Message-ID: <20090720212153.GA6832@infradead.org> (raw)
In-Reply-To: <4A6492AF.3030809@sandeen.net>

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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-07-20 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 15:52 [PATCH] use XFS_CORRUPTION_ERROR in xfs_btree_check_sblock Eric Sandeen
2009-07-20 21:21 ` Christoph Hellwig [this message]
2009-08-01 18:49   ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090720212153.GA6832@infradead.org \
    --to=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.