The volume group I created was as far as I know a "default" setup...
If I'm going to try to re-create the VG, the /dev/hdb1 (dying 200gig Maxtor
) will be dd' d to a 250gig drive, different size. Since I'm dd'ing the
drive and it's creating a partition /dev/hdb1 on the new drive will that
cause a problem? I'm guessing not, since it's essentially identical just
Just thinking out loud here, since I'm trying to fix (xfs_repair) a VG and
the essential data I'm looking for "should" still be intact on the new drive
I just dd'd from the dying one. How will the newly created VG on dev/hda4
know to incorporate the exisitng VG on the second drive /dev/hdb1? and will
it matter if the VG on /dev/hda4 is not identical to the original as long as
it knows to incorporate all of /dev/hdb1 into the VG and the VG name is the
same therefore I can run xfs_repair on it.
Don't you have to set the "blocks" or something when incorporating a new
drive into the VG?
Thanks for all the help and ideas.
On 9/4/05, Iustin Pop <iusty@xxxxxxxxx> wrote:
> On Sat, Sep 03, 2005 at 04:18:00PM -0400, A JM wrote:
> > Yes, I think you understood correctly. The LVM spanned 1 full disk (hdb
> > hdb1) and a partition on another disk (hda4).
> > I might have a "slight" problem re-activating the VG since the original
> > has been rebuilt and therefore doesn't contain what I'm assuming from
> > post, the original VG data? This is not good!
> Uh oh... Could be a problem.
> > Can I re-create the VG on the rebuilt OS and try to incorporate hdb1
> > into the new VG? Then try running xfs_repair?
> Well, if both /dev/hda4 and /dev/hdb1 are available, you should be able
> to recreate it. As far as I know, in default configurations, metadata is
> written on all PVs.
> Try: vgscan and see if you see the VGforMyth volume. If not, try
> pvdisplay /dev/hda4 and pvdisplay /dev/hdb1. Post the output.
> Iustin Pop
[[HTML alternate version deleted]]