From: Dave Chinner <david@fromorbit.com>
To: Matteo Frigo <athena@fftw.org>, 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: Wed, 27 Feb 2013 12:49:00 +1100 [thread overview]
Message-ID: <20130227014900.GY5551@dastard> (raw)
In-Reply-To: <20130227010414.GD1514@agk.fab.redhat.com>
On Wed, Feb 27, 2013 at 01:04:14AM +0000, Alasdair G Kergon wrote:
> (Quick pointers that might be relevant)
>
> EAGAIN, I'm not aware of dm itself returning that on the i/o path.
Neither am I, but it's coming from somewhere in the IO path...
> For 3.8 issues, read dm-devel around https://www.redhat.com/archives/dm-devel/2013-February/msg00086.html
> (I queued the dm-side fixes for linux-next earlier today)
It's reproducable on lots of different kernels, apparently - 3.8,
3.4.33, CentOS 6.3, debian sid/wheezy and Fedora 18 were mentioned
specifically by the OP - so it doesn't look like a recent
regression or constrained to a specific kernel.
> For pvmove, check exactly which version and whether discards are enabled: there
> was a userspace bug for a short period some time ago when discards were enabled.
The version I used to reproduce on a 3.8.0 kernel was:
$ pvmove --version
LVM version: 2.02.95(2) (2012-03-06)
Library version: 1.02.74 (2012-03-06)
Driver version: 4.23.1
>From Debian unstable.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-27 1:49 UTC|newest]
Thread overview: 16+ 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 [this message]
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
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=20130227014900.GY5551@dastard \
--to=david@fromorbit.com \
--cc=athena@fftw.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox