From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 55A447F56 for ; Wed, 27 Feb 2013 17:07:56 -0600 (CST) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay3.corp.sgi.com (Postfix) with ESMTP id 11EABAC002 for ; Wed, 27 Feb 2013 15:07:53 -0800 (PST) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by cuda.sgi.com with ESMTP id vB2zYqGIjYaAamFS for ; Wed, 27 Feb 2013 15:07:51 -0800 (PST) Date: Thu, 28 Feb 2013 10:07:32 +1100 From: Dave Chinner Subject: Re: pvmove corrupting XFS filesystems (was Re: [BUG] Internal error xfs_dir2_data_reada_verify) Message-ID: <20130227230732.GD5551@dastard> References: <87d2vnc34r.fsf@fftw.org> <20130226044039.GM5551@dastard> <20130227010414.GD1514@agk.fab.redhat.com> <20130227014900.GY5551@dastard> <20130227150715.GA4492@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130227150715.GA4492@redhat.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Mike Snitzer Cc: dm-devel@redhat.com, xfs@oss.sgi.com, Matteo Frigo On Wed, Feb 27, 2013 at 10:07:15AM -0500, Mike Snitzer wrote: > On Tue, Feb 26 2013 at 8:49pm -0500, > Dave Chinner wrote: > > > 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 > > Was issue_discards enabled in lvm.conf? $ grep issue_discards /etc/lvm/lvm.conf issue_discards = 0 $ Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs