From: Rich Graves <rgraves@carleton.edu>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] steps to clone a volume group
Date: Mon, 17 Nov 2008 17:27:43 -0600 (CST) [thread overview]
Message-ID: <2142931778.33051391226964463527.JavaMail.root@mail2.its.carleton.edu> (raw)
In-Reply-To: <1755237768.33050951226964401629.JavaMail.root@mail2.its.carleton.edu>
I've had that problem too. Two workarounds. Here's what I usually do:
1a) Map the snapshot LUN to a *different* host than the production machine.
1b) Change the UUID and VG/LV there.
1c) *Then* map the LUN to the production machine.
Alternatively (untested):
2a) service haldaemon stop; service multipathd stop; service lvm2-monitor stop (not sure which of these is really necessary)
2b) Map the snapshot to the production server in the SAN.
2c) Manually add with echo '- - -' > /sys/class/scsi_host/hostN/scan
2d) Change UUID and VG/LV.
2e) Manually remove with echo 1 > /sys/block/sdX/device/delete
2f) service haldaemon start; service multipathd start; service lvm2-monitor start
--
Rich Graves http://claimid.com/rcgraves
Carleton.edu Sr UNIX and Security Admin
CMC135: 507-222-7079 Cell: 952-292-6529
next parent reply other threads:[~2008-11-17 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1755237768.33050951226964401629.JavaMail.root@mail2.its.carleton.edu>
2008-11-17 23:27 ` Rich Graves [this message]
2008-11-18 0:06 ` [linux-lvm] steps to clone a volume group Michael Jensen
2008-11-15 2:37 [linux-lvm] Editing LVM 2 metadata Michael Jensen
2008-11-15 2:55 ` Alasdair G Kergon
2008-11-17 22:58 ` [linux-lvm] steps to clone a volume group Michael Jensen
-- strict thread matches above, loose matches on Subject: below --
2007-11-22 15:18 [linux-lvm] Steps to "clone" " Bryn M. Reeves
2007-11-22 16:05 ` Alasdair G Kergon
2007-11-26 16:58 ` Bryn M. Reeves
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=2142931778.33051391226964463527.JavaMail.root@mail2.its.carleton.edu \
--to=rgraves@carleton.edu \
--cc=linux-lvm@redhat.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 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.