[linux-lvm] more vg problems or oddities...not using dmsetup remove seems to be bad?
support at bettercgi.com
Mon Sep 12 07:33:45 UTC 2011
>> 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.
support at bettercgi.com
Strongbox - The next generation in site security:
Throttlebox - Intelligent Bandwidth Control
Strongbox / Throttlebox affiliate program:
On Sun, 11 Sep 2011 17:44:48 -0700
"Linda A. Walsh" <lvm at 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
> 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
> (hoping system stays up until I get this sorted out!)...
> linux-lvm mailing list
> linux-lvm at redhat.com
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
More information about the linux-lvm