All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matteo Frigo <athena@fftw.org>
To: Dave Chinner <david@fromorbit.com>
Cc: dm-devel@redhat.com, xfs@oss.sgi.com
Subject: Re: [dm-devel] [BUG] pvmove corrupting XFS filesystems (was Re: [BUG] Internal error xfs_dir2_data_reada_verify)
Date: Fri, 08 Mar 2013 06:38:56 -0500	[thread overview]
Message-ID: <87ppza5df3.fsf@fftw.org> (raw)
In-Reply-To: <20130308015723.GA23616@dastard> (Dave Chinner's message of "Fri, 8 Mar 2013 12:57:23 +1100")

Dave Chinner <david@fromorbit.com> writes:

> Add the the patch below. If you still see errors, then they are real
> IO errors from the block device.

This patch fixes the problem for me.

The patch works both when dm-raid1 returns -EIO and when it returns
-EWOULDBLOCK.

Thanks for your help.

Cheers,
Matteo

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

  reply	other threads:[~2013-03-08 11:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  0:47 [BUG] Internal error xfs_dir2_data_reada_verify Matteo Frigo
2013-02-26  4:40 ` [BUG] pvmove corrupting XFS filesystems (was Re: [BUG] Internal error xfs_dir2_data_reada_verify) Dave Chinner
2013-02-26 11:29   ` Matteo Frigo
2013-02-27  1:04   ` [dm-devel] " Alasdair G Kergon
2013-02-27  1:49     ` Dave Chinner
2013-02-27  1:49       ` Dave Chinner
2013-02-27  2:21       ` Matteo Frigo
2013-02-27  2:29         ` Dave Chinner
2013-03-07 12:13         ` Matteo Frigo
2013-03-07 22:31           ` Dave Chinner
2013-03-07 22:50             ` Dave Chinner
2013-03-08  0:09             ` Matteo Frigo
2013-03-08  1:57               ` Dave Chinner
2013-03-08 11:38                 ` Matteo Frigo [this message]
2013-02-27 15:07       ` Mike Snitzer
2013-02-27 15:10         ` Matteo Frigo
2013-02-27 23:07         ` Dave Chinner

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=87ppza5df3.fsf@fftw.org \
    --to=athena@fftw.org \
    --cc=david@fromorbit.com \
    --cc=dm-devel@redhat.com \
    --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.