Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] duplicate volume group names
Date: Thu Apr 17 09:12:02 2003	[thread overview]
Message-ID: <20030417160638.B11844@sistina.com> (raw)
In-Reply-To: <20030414203656.GA7936@ubik>; from pokryfka@druid.if.uj.edu.pl on Mon, Apr 14, 2003 at 10:36:56PM +0200

Michal,

detach the 2nd HDD, vgrename "vg0" to something, reattach the 2nd HDD,
run "vgscan;vgchange -ay" and you should be able to access both.
Keep necessary /etc/fstab changes in mind doing so.

Regular procedure for such VG moves from one computer to another is
"vgchange -an VG ; vgexport VG" on the 1st one, move PVs to the 2nd computer
and run "vgimport VG PVPath [PVPath...]" there.

Regards,
Heinz    -- The LVM Guy --



On Mon, Apr 14, 2003 at 10:36:56PM +0200, MichalAdamczak wrote:
> hi,
> 
> ------------
> 
> # vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "vg0"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume
> group
> 
> # vgchange -a y
> vgchange -- volume group "vg0" already active
> 
> # pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/ide/host2/bus0/target0/lun0/part3" of VG
> "vg0" [55.71 GB / 14.14 GB free]
> pvscan -- inactive PV "/dev/ide/host2/bus0/target1/lun0/part3" of VG
> "vg0" [37.07 GB / 280 MB free]
> pvscan -- total: 2 [92.79 GB] / in use: 2 [92.79 GB] / in no VG: 0 [0]
> 
> ----------
> 
> and the question:
> is it possible to get data from the second hdd if it has the same volume
> name?
> the second hardrive comes from a different computer and has nothing to
> do with the 'vg0' of the first (system) hdd
> 
> do i need to change the name of the volume group name of the system disk
> first?
> 
> regards
> 
> ps. plz respond to private email as i am not subscribed to the list
> 
> -- 
> Michal Adamczak
> pokryfka @ druid.if.uj.edu.pl
> GS dpu C+++ UL+++++ L+++(++++) w--- !tv h*
> I code AND I bathe. (seen on slashdot)
> 
> _______________________________________________
> 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-04-17  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 16:23 [linux-lvm] duplicate volume group names Michal Adamczak
2003-04-17  9:12 ` Heinz J . 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=20030417160638.B11844@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox