From: Thomas Ellis <tellis@redhat.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Restoring data from a SAN based clone/snapshot
Date: Wed, 21 May 2008 16:57:13 +0100 [thread overview]
Message-ID: <48344659.9040401@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
When you take a hardware based clone of a SAN LUN containing a PV/VG and present it to a
system already using the original PV/VG, LVM notices that the both have the same UUID's
and chooses to use one rather than the other.
Using the clone and copying data from it is not initially obvious, so I've added a
procedure to the wiki for $subject:
http://sources.redhat.com/lvm2/wiki/HardwareSnapshotRestore
Please take a look and let me know what your think, feel free to modify/update as you feel
necessary.
regards,
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkg0RlkACgkQOZBvfQY8NVp2EgCfYzUno36yrBlzjzmoD0aD7Gkx
SoIAn0Jz1mlrzuV+Q9RiRbwKmdFIquXL
=C9NG
-----END PGP SIGNATURE-----
reply other threads:[~2008-05-21 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48344659.9040401@redhat.com \
--to=tellis@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).