From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id jB6MejV28406 for ; Tue, 6 Dec 2005 17:40:45 -0500 Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id jB6MebOK005834 for ; Tue, 6 Dec 2005 17:40:37 -0500 Received: by zproxy.gmail.com with SMTP id f1so185831nzc for ; Tue, 06 Dec 2005 14:40:37 -0800 (PST) Message-ID: <87f94c370512061440s6b1b7ca0rffad7f53503309e4@mail.gmail.com> Date: Tue, 6 Dec 2005 17:40:36 -0500 From: Greg Freemyer MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: [linux-lvm] invalid lv in extent map Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: LVM general discussion and development I have recently upgraded a test server from 2.4.x with LVM 1 to 2.6.13 with LVM 2. I can mount my 3 LVs, but when I try to do basic lvm commands I get "invalid lv in extent map". # pvscan invalid lv in extent map Couldn't fill logical volume maps. invalid lv in extent map Couldn't fill logical volume maps. No matching physical volumes found # pvscan --version LVM version: 2.01.14 (2005-08-04) Library version: 1.01.04 (2005-08-02) Driver version: 4.4.0 I did not run vgconvert manually, so I assume I still have LVM1 metadata. This is a test server, so none of the data in the LVs is important, but I hope to be upgrading my live file server soon, so I would like to figure out how to not lose any data. Thanks Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century