<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 07/19/2010 07:14 AM, andiket a wrote:
<blockquote cite="mid:846462.8576.qm@web137317.mail.in.yahoo.com"
type="cite">
<table cellpadding="0" cellspacing="0" border="0">
<tbody>
<tr>
<td
style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit; -x-system-font: none;"
valign="top">Is it possible to specify a different device or to be
specific a different VG than original VG to create a cow store for
snapshot.<br>
<br>
If I have a an LV in VG1 then I don't snapshot to create cow store
(snapshot LV) on same VG but to use VG2.<br>
</td>
</tr>
</tbody>
</table>
</blockquote>
<br>
Short answer: no<br>
<br>
Long answer: support for this would defeat the purpose of volume
groups. VGs have independent metadata so that you can remove them
independently, move between system, and so on. If a misguided soul
were to implement your feature, then the two volume groups would have
to be "locked together" so that removing one or the other would
invalidate the snapshot. For similar reasons, you cannot hardlink
files between unix filesystems.<br>
<br>
If you are using volume groups for the naming only, try using a
separator in your LV names. (LVM lawyers - what are legal chars to
use?) For instance, I know '_' is safe, so for example instead of
vgabc/lv1 and vgdef/lv2, where you are willing to "entangle" vgabc and
vgdef because they are always online together, just make a single
vgroot and<br>
use vgroot/abc_lv1 vgroot/def_lv2.<br>
<br>
BTW, A feature that would make more sense would be hierarchical
namespace for LVs within a VG, i.e. subdirs within the /dev/vg*
directory. Very low priority, and tricky, but would be handy for
naming purposes.<br>
<br>
</body>
</html>