linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Rainer Fügenstein" <rfu@oudeis.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] recover volume group & locical volumes from PV?
Date: Mon, 13 May 2019 17:17:25 +0200	[thread overview]
Message-ID: <842d9f3d-5536-ee5b-71ab-60407cfd5dee@oudeis.org> (raw)
In-Reply-To: <6747eb8e-b15c-dfdd-610b-bc5143368a63@redhat.com>

hi,

> I don't understand how this could have happened by accident.
> lvm2 provides strong detection of duplicated devices.
> It also detects older metadata.

that's what also puzzles me, since I've never had any issues in this 
regard before.

> So you would have to put in 'exact' but just old 'copy' of your device
> and at the same time drop out the original one -� is that what you've 
> made ??

no. this is what happened: (from memory)

/dev/sda5 = only PV containing vg_sh64

about 2 months ago:

pvcreate /dev/sdc1 (temp. HD)
vgextend vg_sh64 /dev/sdc1
pvmove vg_sh64 /dev/sda5     (move VG from old to temp HD)
vgreduce vg_sh64 /dev/sda5

- replace "old" sda with a new, bigger one
- create same partition layout

pvcreate /dev/sda5
vgextend vg_sh64 /dev/sda5
pvmove vg_sh64 /dev/sdc1   (move everything back to new HD)
vgreduce vg_sh64 /dev/sdc1

what I *DID FORGET* then was to issue "pvremove /dev/sdc1"

a few days ago, I inserted the old temp HD sdc into the SATA hot swap 
bay and powered it on. shortly after that the system behaved strangely. 
issued "dmesg" and saw a lot of error messages regarding SATA. 
unfortunately, memory is blurry from then on since I entered panic mode.

Did a graceful shutdown though (closed all programms, executed 
"poweroff"). from this moment on, VG on /dev/sda5 was gone.

can't rule out that powering on sdc in the hot plug bay caused havoc on 
the SATA bus, just when lvm was doing some housekeeping.

> VG & LV are just 'terms' - there is no 'physical-conte
> lvm2 provides command:� 'vgcfgrestore' - which can restore your older 
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

thanks for the information (also to Roger). I managed to recover a 
promising LVM text file from lost+found on the temp disk. will try to 
restore it as soon as I'm back home again.

thanks - and wish me luck ;-)

  reply	other threads:[~2019-05-13 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-11 22:52 [linux-lvm] recover volume group & locical volumes from PV? "Rainer Fügenstein"
2019-05-12  0:09 ` Roger Heflin
2019-05-13  8:37 ` Zdenek Kabelac
2019-05-13 15:17   ` Rainer Fügenstein [this message]
2019-05-15 16:55   ` Rainer Fügenstein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=842d9f3d-5536-ee5b-71ab-60407cfd5dee@oudeis.org \
    --to=rfu@oudeis.org \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).