linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm2 and external enclosures
Date: Mon, 20 Jul 2009 00:03:20 -0500	[thread overview]
Message-ID: <4A63FA98.6010207@cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0907200016130.9385@bmsred.bmsi.com>

On 2009-07-19 23:30, Stuart D. Gathman wrote:
> On Sun, 19 Jul 2009, Ron Johnson wrote:
> 
>> (The purpose of this "exercise" is to implement a backup strategy.)
> 
> ...
> 
>> Any thoughts on getting lvm2 to play nice with dynamic devices?
> 
> You have to do "vgchange -an backupvgxx" before removing the 
> dynamic volumes.  It is possible to deactivate the vg after

Worked like a charm.  Thanks!

-- 
Scooty Puff, Sr
The Doom-Bringer

      reply	other threads:[~2009-07-20  5:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 21:50 [linux-lvm] lvm2 and external enclosures Ron Johnson
2009-07-20  4:30 ` Stuart D. Gathman
2009-07-20  5:03   ` Ron Johnson [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=4A63FA98.6010207@cox.net \
    --to=ron.l.johnson@cox.net \
    --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).