From: Turbo Fredriksson <turbo@bayour.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] one PV crashed
Date: Thu Feb 7 04:32:02 2002 [thread overview]
Message-ID: <87bsf1eg6b.fsf@papadoc.bayour.com> (raw)
In-Reply-To: <20020201111151.B15491@sistina.com>
Quoting "Heinz J . Mauelshagen" <mauelshagen@sistina.com>:
> Buy a replacemeent drive (say /dev/sdg1 ;-) and run
>
> fdisk # to partition it the same way the broken one was
> pvcreate /dev/sdg1
> vgcfgrestore -f /etc/lvmconf/vg1.conf -n vg1 /dev/sdg1
> vgscan
Oki, since I had a LVM with broken loop support, I'll try with a spare disk...
----- s n i p -----
[papadoc.root]# pvcreate /dev/sdh1
pvcreate -- physical volume "/dev/sdh1" successfully created
[papadoc.root]# vgcfgrestore -f /etc/lvmconf/vg1.conf -n vg1 /dev/sdh1
vgcfgrestore -- physical volume "/dev/sdh1" doesn't belong to volume group "vg1"
[papadoc.root]# vgcfgrestore -f /etc/lvmconf/vg1.conf -n vg1 -o /dev/sdg1 /dev/sdh1
vgcfgrestore -- size of physical volume /dev/sdh1 differs from backup
----- s n i p -----
I'm not sure exactly how big my previous (now crashed) sdg disk was, or how big
the sdg1 partition was...
How do I:
1. Find out _exactly_ how big the sdg1 partition was (the only
number I have is '15.5Gb')?
or
2. Use the existing sdh1 even though the size don't match?
> After either of the above aproaches you need to lvreduce/lvremove those
> LVs which had extents allocated on the failed drive.
>
> You can figure out which those are by
>
> pvdisplay -v /dev/sdg1
----- s n i p ----
[papadoc.root]# pvdisplay -v /dev/sdh1
pvdisplay -- getting physical volume size
pvdisplay -- "/dev/sdh1" is a new physical volume of 2.22 GB
----- s n i p ----
Not nearly the same size as the original sdg1, but....
cracking Saddam Hussein Albanian class struggle smuggle BATF Legion of
Doom Cuba ammonium DES 747 767 pits Serbian plutonium
[See http://www.aclu.org/echelonwatch/index.html for more about this]
next prev parent reply other threads:[~2002-02-07 4:32 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 [this message]
2002-02-15 5:50 ` Turbo Fredriksson
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=87bsf1eg6b.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