From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Dangerous Recipes
Date: Tue Jan 28 02:17:01 2003 [thread overview]
Message-ID: <20030128081507.GA31789@tykepenguin.com> (raw)
In-Reply-To: <022501c2c644$92634410$4b66699f@win.doc.state.vt.us>
On Mon, Jan 27, 2003 at 03:42:13PM -0500, Joseph Kezar wrote:
> I have a single shared SCSI JBOD. And it makes up my VolumeGroupMailData.
>
> It is mounted read/write by only 1 node at any given time. This is strictly
> enforced.
>
> Although, at boot both nodes vgchange -a y the Volume Group.
> So it is picked up in vgscan as an active VG on node1 and node2
> I am aware if I need to make a change, like adding a Logical Volume,
> Extending/Reducing a Logical Volume, or adding/subtracting a physical volume
> that the volume must be deactivated on the secondary node(in my case node
> 2).
>
> If everything goes well enforced, am I still in trouble or at risk of data
> corruption?
If you are careful it should be fine.
What you must always remember to do is "vgchange -an" on the secondary node
before doing the metadata changes, then a "vgscan;vgchange -ay" on that node
after the metadata changes.
--
patrick
prev parent reply other threads:[~2003-01-28 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 14:43 [linux-lvm] Dangerous Recipes Joseph Kezar
2003-01-28 2:17 ` Patrick Caulfield [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=20030128081507.GA31789@tykepenguin.com \
--to=caulfield@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