From: Turbo Fredriksson <turbo@bayour.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] one PV crashed
Date: Fri Feb 15 05:50:02 2002 [thread overview]
Message-ID: <87wuxf6k3a.fsf@papadoc.bayour.com> (raw)
In-Reply-To: <87bsf1eg6b.fsf@papadoc.bayour.com>
>>>>> "Turbo" == Turbo Fredriksson <turbo@bayour.com> writes:
Turbo> Oki, since I had a LVM with broken loop support, I'll try
Turbo> with a spare disk...
Turbo> [papadoc.root]# vgcfgrestore -f /etc/lvmconf/vg1.conf -n
Turbo> vg1 -o /dev/sdg1 /dev/sdh1 vgcfgrestore -- size of physical
Turbo> volume /dev/sdh1 differs from backup ----- s n i p -----
Turbo> I'm not sure exactly how big my previous (now crashed) sdg
Turbo> disk was, or how big the sdg1 partition was...
Oki, I managed to pvcreate my new sdh1, and then a vgcfgrestore.
vgcfgrestore -f /etc/lvmconf/vg1.conf -n vg1 -o /dev/sdg1 /dev/sdh1
This went ok, but 'pvscan -u' is behaving (?) strangly...
----- s n i p -----
[papadoc.root]# pvscan -u
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sdb1 " with UUID "ofZCeT-O16H-Df0h-4KoB-xQhm-lc24-67dZvk" is associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/sdc1 " with UUID "xN0MF7-xKU0-Uk3L-g8Pw-0YfH-fS3V-zgFA66" is associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/sdd10" with UUID "5V0XNB-gA87-OU66-1iza-cvsz-xQ2q-6DEbyH" is associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/sde1 " with UUID "Bdm7PX-50Dq-hC6R-yXmv-DDq1-n6Nx-4ohaKK" is associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/sdf1 " with UUID "QnqfyA-fOTB-J1Pp-4be5-t6QU-bGjS-i2BKf2" is associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/sdh1 " with UUID "ZNODti-EFFz-rGID-HYyh-kg7Z-yDCe-LLbXBv" is in no VG [15.55 GB]
pvscan -- total: 6 [50.39 GB] / in use: 5 [34.84 GB] / in no VG: 1 [15.55 GB]
----- s n i p -----
Running vgscan (as directed) gives me:
----- s n i p -----
[papadoc.root]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume group
----- s n i p -----
Ideas how to get my VG up and running again?
cryptographic Ft. Bragg NORAD plutonium 747 Legion of Doom Serbian
Saddam Hussein munitions Noriega supercomputer colonel fissionable
smuggle kibo
[See http://www.aclu.org/echelonwatch/index.html for more about this]
next prev parent reply other threads:[~2002-02-15 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 4:01 [linux-lvm] one PV crashed Turbo Fredriksson
2002-02-01 4:16 ` Heinz J . Mauelshagen
2002-02-01 4:52 ` Turbo Fredriksson
2002-02-01 5:08 ` Heinz J . Mauelshagen
2002-02-01 5:17 ` Turbo Fredriksson
2002-02-01 8:22 ` Turbo Fredriksson
2002-02-06 5:01 ` Turbo Fredriksson
2002-02-06 13:58 ` Heinz J . Mauelshagen
2002-02-07 3:41 ` Turbo Fredriksson
2002-02-07 4:32 ` Turbo Fredriksson
2002-02-15 5:50 ` Turbo Fredriksson [this message]
2002-02-15 6:01 ` Turbo Fredriksson
2002-02-15 7:57 ` Heinz J . Mauelshagen
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=87wuxf6k3a.fsf@papadoc.bayour.com \
--to=turbo@bayour.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox