Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932126AbXAIPPn (ORCPT ); Tue, 9 Jan 2007 10:15:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932146AbXAIPPn (ORCPT ); Tue, 9 Jan 2007 10:15:43 -0500 Received: from mx1.redhat.com ([66.187.233.31]:41957 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932126AbXAIPPn (ORCPT ); Tue, 9 Jan 2007 10:15:43 -0500 Date: Tue, 9 Jan 2007 15:15:39 +0000 From: Alasdair G Kergon To: Dave Jones Cc: Linux Kernel Subject: Re: lvm backwards compatability Message-ID: <20070109151539.GW21980@agk.surrey.redhat.com> Mail-Followup-To: Alasdair G Kergon , Dave Jones , Linux Kernel References: <20070108230111.GC14548@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070108230111.GC14548@redhat.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 970 Lines: 25 On Mon, Jan 08, 2007 at 06:01:11PM -0500, Dave Jones wrote: > Did backwards compatability with old LVM metadata break intentionally > in 2.6.19 ? I have a volume that mounts just fine in 2.6.18, > but moving to 2.6.19 gets me this.. No - and at first sight that's not a kernel device-mapper problem. Please grab some diagnostics: run the lvmdump script (present in the newest packages) or from here: http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/LVM2/scripts/lvm_dump.sh?content-type=text/plain&cvsroot=lvm2 with the -a and -m flags. [NB If you use dm-crypt and have userspace device-mapper < 1.02.13 you need to remove the encryption keys from the 'dmsetup' output by hand.] Alasdair -- agk@redhat.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/