linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Timms <dtimms@iinet.net.au>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshots can't be deactivated
Date: Fri, 20 Jul 2007 07:50:54 +1000	[thread overview]
Message-ID: <469FDCBE.2010403@iinet.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0707191047010.6647-100000@bmsred.bmsi.com>

Stuart D. Gathman wrote:
> On Wed, 18 Jul 2007, Joachim Banzhaf wrote:
> 
>>> Are my steps right in principle? Did I forget to do something before or
>>> after removing?
>> I am by no means an expert on lvm, so dont take this too seriously: shouldn't 
>> there be an lvchange -an yourlv before lvremove? Maybe this active status is 
>> still hanging around somewhere although you can force the remove?
> 
> When I try lvchange -an C4_SNAP, it always fails.  So I have had to force
> the lvremove in the backup script.  I am nervous about this, and already asked
> why this is the case.  When reading about the "active" flag, it seems
> to have something to do with shared SAN storage volume groups, so perhaps we
> are not supposed to deactivate LVs for simple single machine systems.  But the
> error from lvremove is disconcerting.  If I force it, what if there is
> a *different* error that I really *don't* want to force?
Perhaps the command produces an errorlevel that you could test against, 
and only continue when you get the expected error ?

DaveT.

  reply	other threads:[~2007-07-19 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 14:33 [linux-lvm] snapshots can't be deactivated Falko Zurell
2007-07-18 11:37 ` Joachim Banzhaf
2007-07-19  7:48   ` Falko Zurell
2007-07-19 14:52   ` Stuart D. Gathman
2007-07-19 21:50     ` David Timms [this message]
2007-07-20  6:24       ` Falko Zurell

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=469FDCBE.2010403@iinet.net.au \
    --to=dtimms@iinet.net.au \
    --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).