From: prajnoha@sourceware.org <prajnoha@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/doc tagging.txt
Date: 22 Nov 2011 13:54:06 -0000 [thread overview]
Message-ID: <20111122135406.7067.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: prajnoha at sourceware.org 2011-11-22 13:54:05
Modified files:
doc : tagging.txt
Log message:
--addtag instead of --tag
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/tagging.txt.diff?cvsroot=lvm2&r1=1.1&r2=1.2
--- LVM2/doc/tagging.txt 2004/11/17 18:34:49 1.1
+++ LVM2/doc/tagging.txt 2011/11/22 13:54:05 1.2
@@ -85,7 +85,7 @@
From any machine in the cluster, add db1 to the list of machines that
activate vg1/lvol2:
- lvchange --tag @db1 vg1/lvol2
+ lvchange --addtag @db1 vg1/lvol2
(followed by lvchange -ay to actually activate it)
@@ -98,10 +98,10 @@
Option (i) - centralised admin, static configuration replicated between hosts
# Add @database tag to vg1's metadata
- vgchange --tag @database vg1
+ vgchange --addtag @database vg1
# Add @fileserver tag to vg2's metadata
- vgchange --tag @fileserver vg2
+ vgchange --addtag @fileserver vg2
lvm.conf: (Identical on every machine)
tags {
@@ -122,17 +122,17 @@
}
In the event of the fileserver host going down, vg2 can be brought up
- on fsb1 by running *on any node* 'vgchange --tag @fileserverbackup vg2'
+ on fsb1 by running *on any node* 'vgchange --addtag @fileserverbackup vg2'
followed by 'vgchange -ay vg2'
Option (ii) - localised admin & configuation
(i.e. each host holds *locally* which classes of volumes to activate)
# Add @database tag to vg1's metadata
- vgchange --tag @database vg1
+ vgchange --addtag @database vg1
# Add @fileserver tag to vg2's metadata
- vgchange --tag @fileserver vg2
+ vgchange --addtag @fileserver vg2
lvm.conf: (Identical on every machine - global settings)
tags {
next reply other threads:[~2011-11-22 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:54 prajnoha [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-27 13:39 LVM2/doc tagging.txt mbroz
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=20111122135406.7067.qmail@sourceware.org \
--to=prajnoha@sourceware.org \
--cc=lvm-devel@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.