From: Dave Chinner 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 Message-ID: <20130227014900.GY5551@dastard> References: <87d2vnc34r.fsf@fftw.org> <20130226044039.GM5551@dastard> <20130227010414.GD1514@agk.fab.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20130227010414.GD1514@agk.fab.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Matteo Frigo , dm-devel@redhat.com, xfs@oss.sgi.com List-Id: dm-devel.ids 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