From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 11 Jan 2015 17:33:36 +0000 From: Alasdair G Kergon Message-ID: <20150111173336.GA19834@agk-dp.fab.redhat.com> References: <2368A3FCF9F7214298E53C823B0A48EC042ECF3F@AMSPEX01CL02.citrite.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <2368A3FCF9F7214298E53C823B0A48EC042ECF3F@AMSPEX01CL02.citrite.net> Subject: Re: [linux-lvm] deleted LV recovery: understanding metadata format and determining LV extents 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" Content-Transfer-Encoding: 7bit To: Thanos Makatos Cc: "linux-lvm@redhat.com" On Sat, Jan 10, 2015 at 06:12:03PM +0000, Thanos Makatos wrote: > Hi, I'm working on a case where a bunch of logical volumes were deleted but now we need them back. We have disabled archives and back ups in lvm.conf. They way I am trying to approach the problem is to examine LVM's metadata (the first MB of the block device) and determine whether the extents used by these logical volumes have been assigned to other logical volumes. So start by looking at the contents of the metadata areas and see if they still contain backups you can extract. They are circular buffers so look for the seqno field which is incremented each time the metadata is changed. lvmdump -m can grab the metadata. 'pvck -v $device' contains the beginnings of code to extract the backups Alasdair