From: Ray Morris <support@bettercgi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] more vg problems or oddities...not using dmsetup remove seems to be bad?
Date: Mon, 12 Sep 2011 02:33:45 -0500 [thread overview]
Message-ID: <20110912023345.476db018@bettercgi.com> (raw)
In-Reply-To: <4E6D5600.4060008@tlinx.org>
>> tried to remove an unmounted active snapshot.
>>
>> lvremove said it wouldn't remove an active snapshot.
>>
>> Tried -an -- can't change active snapshot.
> Use lvremove -f
What's directly in the LV? A partition perhaps? A raid block?
If it says that it can't be removed because it's in active use,
busy, it's probably telling you the truth. I've had this happen
a couple of times. In one case, it held a virtual machine with
a partition I had mapped using kpartx, so I had to use kpartx
to unmap that partition. I think the other time the LV was itself
a PV, or else it was shared using gnbd.
--force means, in my opinion at least, "Yes, I know what I'm doing.
I understand why the system is saying I better not do this, but
I want to force it to happen anyway". When it's used to mean "I don't
understand what's going on, I don't know why this is a bad idea,
but do it anyway", that sounds to me like a recipe for problems.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On Sun, 11 Sep 2011 17:44:48 -0700
"Linda A. Walsh" <lvm@tlinx.org> wrote:
>
>
> tried to remove an unmounted active snapshot.
>
> lvremove said it wouldn't remove an active snapshot.
>
> Tried -an -- can't change active snapshot.
>
>
> Tried turning off monitoring --monitor -n
> It gave no message
> tried removing again...can't remove active snap
>
> tried --ignoremonitoring
>
> no message but still can't remove
>
> tried -- merging it...
>
> Said it couldn't merge with open origin,
> then merging with origin on next activation...
>
> Now still can't remove, but says "
> Can't remove merging snapshot logical volume
> "Home-2011.09.03-00.28.36" ...
>
> decided to try dmsetup remove --
>
> it couldn't remove it either -- resource/device busy...
>
> So now I'm concerned...is it going to try to merge back any changes
> it recorded by reversing them?
>
> i.e. put the original volume back the way it was when the snapshot
> started?
>
> Says it couldn't do it on open volume -- does that mean it won't
> start this until I reboot,
> then it will take a long time to become active?
>
> seems like the dmsetup remove of the parts was the safest way to
> kill off an active snapshot...but this feels contorted.
>
> I'm wondering if I really want this 'merge' it wants to do...and if
> not, how do I abort
> it?
>
> Thanks!
>
> (hoping system stays up until I get this sorted out!)...
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2011-09-12 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 0:44 [linux-lvm] more vg problems or oddities...not using dmsetup remove seems to be bad? Linda A. Walsh
2011-09-12 3:04 ` Stuart D. Gathman
2011-09-12 3:14 ` Stuart D. Gathman
2011-09-12 4:05 ` Linda A. Walsh
2011-09-12 4:08 ` Linda A. Walsh
2011-09-12 7:33 ` Ray Morris [this message]
2011-09-12 13:57 ` Stuart D. Gathman
2011-09-12 17:27 ` [linux-lvm] How to stop MERGE? (was Re: more vg problems or oddities...not using dmsetup remove seems to be bad?) Linda A. Walsh
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=20110912023345.476db018@bettercgi.com \
--to=support@bettercgi.com \
--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 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.