From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] How to stop MERGE? (was Re: more vg problems or oddities...not using dmsetup remove seems to be bad?)
Date: Mon, 12 Sep 2011 10:27:35 -0700 [thread overview]
Message-ID: <4E6E4107.70802@tlinx.org> (raw)
In-Reply-To: <alpine.LRH.2.00.1109120949090.9046@bmsred.bmsi.com>
Stuart D. Gathman wrote:
>
> In the OP problem, we don't know the exact error message, so perhaps
> the snapshot really was open. In any case, she needs to stop the
> merge from happening the next time the LV is activated.
---
I've only seen 1 error message ..
Ah....here are the two messages...this ****IS NOT*** a snapshot volume...
it's a static volume!
Here's lvs. I'm going to remove the oldest static 'snap' (not an active
snapshot, but a copy of one that existed back then. It's currently
mounted, .. (lv Home-2011.07.20-13.43.15; you'll never guess when the
snapshot was started or what the base LV was.. ;-) )...
It's currently mounted, and no 's' in status... (i.e. not an active
snapshot).
NOTE, poor 'Home' has 'O' status -- thinks it is MERGing, but nothing
for it to MERGE with! -- this is a problem waiting to happen that I need
to ABORT.
# lvs
LV VG Attr LSize
Backups Backups -wi-ao 10.91t
Home Home+Space Owi-ao 1.00t
Home-2011.07.20-13.43.15 Home+Space -wi-ao 171.00g <-about to remove
Home-2011.07.25-16.24.53 Home+Space -wi-ao 1.88g
....
Home-2011.08.31-07.34.53 Home+Space -wi-ao 1.86g
Home-2011.09.04-19.25.08 Home+Space swi-ao 1.00t Home 1.25
Home.diff Home+Space -wi-ao 512.00g
# lvremove /dev/Home+Space/Home-2011.07.20-13.43.15 # first w/o
umounting it...
Can't remove open logical volume "Home-2011.07.20-13.43.15"
ok... so lets. unmount it...
# umount /home/snapdir/@GMT-2011.07.20-13.43.15
# lvremove /dev/Home+Space/Home-2011.07.20-13.43.15
Do you really want to remove active logical volume
Home-2011.07.20-13.43.15? [y/n]: y
Logical volume "Home-2011.07.20-13.43.15" successfully removed
^^^
This isn't helpful...as it's not *really* active in any way to the OS...
though it might still be 'activated'...(that's why I'm trying to
remove it...!)...
It was created w/lvcreate, so ... opposite of lvcreate would be
lvremove, no?... there is no 'lvucreate'.. ;-/
FWIW...Home is even more confused...
Thought it was going to merge with a volume from 2011.09.03-xxxx, but
dmsetup remove on /dev/Home+Space/Home-2011.09.03-xxxx suceeded w/o force
as well as:
/dev/Home+Space/Home-2011.09.03-xxxx-cow
So now, /Home... what's it going to merge w/? (Garbage likely...)...
That's what I love about the M5 computer, er, LVM2 Merge option:
"No off switch"...
(last crewman who tried to pull the plug got zapped...didn't know lvm
was so dangerous!...;-) ).
prev parent reply other threads:[~2011-09-12 17:27 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
2011-09-12 13:57 ` Stuart D. Gathman
2011-09-12 17:27 ` Linda A. Walsh [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=4E6E4107.70802@tlinx.org \
--to=lvm@tlinx.org \
--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.