From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: hjm@redhat.com
Subject: Re: [linux-lvm] It never rains...
Date: Mon, 22 Mar 2004 11:04:43 +0100 [thread overview]
Message-ID: <20040322100443.GA11567@redhat.com> (raw)
In-Reply-To: <OFA503F7CB.EA7425E4-ON80256E5D.002A1936-80256E5D.002BCF6E@uk.ibm.com>
On Sat, Mar 20, 2004 at 08:02:03AM +0000, Chris Laycock wrote:
> Hi All,
>
> Had a bit a disaster, lost 1 disk from a 3 disk VG and the root partition!
> All on fully patched RH 9 system.
> I realise that I need to attach the 2 remaining PV to a LV and VG but if I
> do the usual vgcreate, lvcreate & pvcreate I'll end up with two dataless
> disks.
No, you need to replace the failed drive, pvcreate the new one (same size
as the dead one!) and vgcfgrestore the LVM metadata (see /etc/lvmconf/ and
the vgcfgrestore manual page) to it in order to be able to vgscan+vgchange
successfully.
Presumably your 2 surviving drives have most of the data allocated you should
be able to gain access to (most of) your data.
lvdisplay -v ... and pvdisplay -v ... are your friends to display the
actual mappings of LVs to PVs and vice/versa once you recovered
with vgcfgrestore.
> I luckly do have backups of some of the more important data but there not
> a recenct as I'd like and don't contain all of the data or the root
> partition.
If critical data is allocated to the dead drive (eg, start of LV and
a contained filesystem), you're in trouble and your (out-of-date) backup
is your best bet.
FYI: LVM2 has a --partial option for vgchange which will activate your VG
ignoring any missing PVs.
Regards,
Heinz -- The LVM Guy --
>
> Outputs from:
>
> vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of
> volume group "datavg" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume
> group
>
> pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/sda1" is associated to unknown VG "datavg"
> (run vgscan)
> pvscan -- inactive PV "/dev/hdc1" is associated to unknown VG "datavg"
> (run vgscan)
> pvscan -- total: 2 [45.75 GB] / in use: 2 [45.75 GB] / in no VG: 0 [0]
>
> pvdisplay /dev/hdc1
>
> --- Physical volume ---
> PV Name /dev/hdc1
> VG Name datavg
> PV Size 37.28 GB [78172227 secs] / NOT usable 4.19 MB [LVM:
> 165 KB]
> PV# 2
> PV Status available
> Allocatable yes (but full)
> Cur LV 1
> PE Size (KByte) 4096
> Total PE 9541
> Free PE 0
> Allocated PE 9541
> PV UUID vozLHH-585D-SSjH-XM9b-A8g2-888k-5tZWI0
>
> The two remaining disks are /dev/hdc1 & /dev/sda1
>
> Thanks in advance
>
> Regards,
> Chris.
>
> -------------------
> Chris Laycock
> IT Specialist
> IBM Global Services (IDO)
>
> LITS, Stevenage
> Mail point: K3 STEV UK
> Email: LaycockC@uk.ibm.com
> Tel : (01438) 76-9460 (internal: 44-9460)
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-03-22 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 8:02 [linux-lvm] It never rains Chris Laycock
2004-03-22 10:04 ` Heinz Mauelshagen [this message]
2004-03-22 16:20 ` Chris Laycock
2004-03-23 14:58 ` Heinz Mauelshagen
2004-03-26 20:08 ` Chris Laycock
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=20040322100443.GA11567@redhat.com \
--to=mauelshagen@redhat.com \
--cc=hjm@redhat.com \
--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