All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: Thomas Berton <thomas.berton@howest.be>
Cc: hjm@redhat.com,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Hard disk failure, restore problem
Date: Wed, 17 Mar 2004 15:34:13 +0100	[thread overview]
Message-ID: <20040317143413.GB14348@redhat.com> (raw)
In-Reply-To: <40561772.5070302@howest.be>


Thomas,

don't run vgscan after the procedure below.

Remember this is a workaround *just* to get you to the point to be able
to backup your data and recreate your VG.

Run vgmknodes to create your device nodes in /dev/bigspace/
after step "vgchange -ay" below.

Regards,
Heinz    -- The LVM Guy --


On Mon, Mar 15, 2004 at 09:52:02PM +0100, Thomas Berton wrote:
> Hello,
> 
> I've done
> 
> > o identify your actual metadata backup (say, bigspace.conf)
> >
> > o mkdir /etc/lvmtab.d
> >
> > o cp bigspace.conf /etc/lvmtab.d/bigspace
> >
> > o echo -ne "bigspace\0" > /etc/lvmtab
> >
> > o vgchange -ay
> 
> 
> after being sure to restore the metadata I have
> 
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/hdg1" of VG "bigspace" [74.47 GB / 768 MB free]
> pvscan -- inactive PV "/dev/hde1" of VG "bigspace" [149 GB / 0 free]
> pvscan -- inactive PV "/dev/hdf1" of VG "bigspace" [149 GB / 139.16 GB free]
> pvscan -- inactive PV "/dev/hdc1" of VG "bigspace" [111.75 GB / 0 free]
> pvscan -- inactive PV "/dev/hdd1" of VG "bigspace" [74.47 GB / 0 free]
> pvscan -- inactive PV "/dev/hda1" of VG "bigspace" [74.47 GB / 8.22 GB free]
> pvscan -- inactive PV "/dev/hdb1" of VG "bigspace" [74.47 GB / 0 free]
> pvscan -- total: 7 [708 GB] / in use: 7 [708 GB] / in no VG: 0 [0]
> 
> 
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- only found 17904 of 17876 LEs for LV /dev/bigspace/bigspace1 (0)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get
> data of volume group "bigspace" 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
> 
> => after the vgscan the echo -ne "bigspace\0" > /etc/lvmtab is gone gone
> again....
> 
> [root@ment root]# lvscan
> lvscan -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please
> run vgscan
> 
> after doing the vgscan, I get
> 
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/hdg1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- inactive PV "/dev/hde1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- inactive PV "/dev/hdf1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- inactive PV "/dev/hdc1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- inactive PV "/dev/hdd1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- inactive PV "/dev/hda1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- inactive PV "/dev/hdb1"  is associated to unknown VG
> "bigspace" (run vgscan)
> pvscan -- total: 7 [708 GB] / in use: 7 [708 GB] / in no VG: 0 [0]
> 
> again.
> 
> 
> the /dev/bigspace/bigspace1 doesn't exists, so I can't mount.
> 
> should I recreate bigspace and force an import ?
> 
> I 've alse rebooted once after the vgchange -ay, but he also didn't find
> the bigspace.
> 
> thanx again for your help!!
> 
> kind regards,
> Thomas.

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2004-03-17 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12  5:18 [linux-lvm] Hard disk failure, restore problem Thomas Berton
2004-03-15 12:47 ` Heinz Mauelshagen
2004-03-15 20:52   ` Thomas Berton
2004-03-17 14:34     ` Heinz Mauelshagen [this message]

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=20040317143413.GB14348@redhat.com \
    --to=heinzm@redhat.com \
    --cc=hjm@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=thomas.berton@howest.be \
    /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.