All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Erroneously formatted PV; 'vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group'...
Date: Mon Feb 10 07:47:01 2003	[thread overview]
Message-ID: <20030210144322.A5997@sistina.com> (raw)
In-Reply-To: <000301c2d06c$99f7e280$0400000a@lenina>; from tpmaerk@gmx.net on Sun, Feb 09, 2003 at 07:53:56PM +0100

Tim-Patrick,

with your root on LV setup you either need:


an emergency boot media with LVM1 on it _and_ /etc/lvmconf/* backup in
order to restore you LVM metadata using vgcfgrestore presuming you setup
your partitions exactly the way they were before ("vgscan;vgchange -ay" after
metadata restore)

- or -

an emergency boot media with LVM2/device-mapper on it to
run "vgscan ; vgchange --partial -a y" in order to
access your partioal VG without the gone partition

- or -

that LVM2 boot media to restore the metadata.

- or -

to attach your HDDs to another LVM equipped system to repair the
volume group configuration

Regards,
Heinz    -- The LVM Guy --


On Sun, Feb 09, 2003 at 07:53:56PM +0100, Tim-Patrick Märk wrote:
> Hello,
> 
> two days ago i installed a new HDD and added it to my VG 'vg1'
> (partition id '8e' + 'pvcreate /dev/hdb1' + 'vgextend vh1 /dev/hdb1').
> A bit later I erroneously formatted '/dev/hdb1' by 'mkfs.xfs /dev/hdb1'.
> I ran 'vgscan' and 'pvscan' and the made a smiliar output like it is
> shown on
> http://lists.sistina.com/pipermail/linux-lvm/2002-August/011947.html -
> but i have only two PVs in my VG 'vg1': '/dev/hdc1' and '/dev/hdd2'.
> I don't remember what i exactly did with '/dev/hdb' after that (it was
> late...), but as a result I 'fdisked' the partition table away...
> There was no data on '/dev'hdb' (except the LVM metadata), so no 'real'
> data needs to be recovered (at least i hope so).
> 
> All in all, I can't access the VG 'vg1' (PVs: '/dev/hdc1' + '/dev/hdd2')
> with the 3 LVs 'root', 'storage' and 'swap' any more. 
> 
> Now you could advise me to run 'vgcfgrestore', but i regretfully must
> say that i rebooted my box and as the name of the LV 'root' implies, my
> root-filesystem was on it, so the system doesn't boot anymore *doh*...
> 
> Summary:
> - 1 VG: 'vg1'
> - 2 (3) PVs: '/dev/hdc1' + '/dev/hdd2' + for a short time (see above)
> '/dev/hdb1'
> - 3 LVs: 'root', 'storage' and 'swap'
> - Filesystem on all LVs: XFS
> 
> Fortunately i have a separated 'backup system' on another HDD, which
> doesn't use LVM nor XFS, but simply ext2, so i can work with it
> temporarily to fix this disaster.
> 
> I think the problem is, that the VG 'vg1' still thinks, it would consist
> of 3 PVs, but only 2 are there.
> But because no VG is found by 'vgscan' (see link above), i can't remove
> '/dev/hdb1' by 'vgreduce vg1 /dev/hdb1' and so on...
> 
> Is there any way to generate metadata for '/dev/hdb1' to make it known
> by 'vg1' or remove '/dev/hdb1' from 'vg1'?!
> 
> I'm very despaired and would be gladdened by every answer.
> If you need any details, just ask.
> 
> P.S.: This is not intended to be a cross-posting; I only had problems
> submitting my first one.
> 
> Kind regards and thanks in advance
> 
> Tim-Patrick Märk
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.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                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-02-10  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 12:55 [linux-lvm] Erroneously formatted PV; 'vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group' Tim-Patrick Märk
2003-02-10  7:47 ` Heinz J . Mauelshagen [this message]
2003-02-10  8:38   ` [linux-lvm] what is means in /proc/lvm/global abbireddy venkatram reddy
2003-02-11  9:36     ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2003-02-11 18:44 [linux-lvm] Erroneously formatted PV; 'vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group' Tim-Patrick Märk

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=20030210144322.A5997@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.