I might as well nuke the merge....I'd have to restore 2 images to
restore all the files
to this morning....if something went bad, but if I wait around...
I can't see it merging block diffs on an actively mounted file system...that
would just be insane!
really seems like best thing would be to nuke the merge somehow, then
wouldn't
have to resort to backups...
Restoring a TB of data takes a bit of time...
The file system it's trying to merge to is my home dir...
(where all my work goes...;-)...
But while past performance is no guarantee of future performance, currently
my system's uptime stands at 44 days, so it could be a while before said
merge
happens, or ... could happen sooner if I 'try to fix it'....;-)
(power is on UPS, so usually reboots happen because I do something --
usually planned,
but occasionally after shooting one's self in foot...)...
Since it can't start the merge...seems like there should be a way to
stop it w/o causing problems.
**--case in point re:shooting self in foot -- merging 8 day old snap
w/current vol in trying to
work around bugs...*sigh*
You may be right...the force option may be less painful that fixing this
merge thing
if it goes south...
Stuart D. Gathman wrote:
On Sun, 11 Sep 2011, Stuart D. Gathman wrote:
On Sun, 11 Sep 2011, Linda A. Walsh wrote:
tried -- merging it...
Ooops. You likely did not want that. That reverts the origin volume
to the snapshot by copying the original data for updated sectors from
the snapshot. This is an extremely useful feature, but *not* when
you invoke it accidentally!
I'm wondering if I really want this 'merge' it wants to do...and if
not, how do I abort it?
If it is really delayed until boot (or close), then you have a chance
to abort
it, but I don't know how. I hope an expert answers. Meanwhile, I'll
peruse the man page to see if it talks about delayed merge.
The man page says:
If both the origin and snapshot volume are not open the merge will
start
immediately. Otherwise, the merge will start the first time
either the
origin or snap??? shot are activated and both are closed. Merging a
snapshot
into an origin that cannot be closed, for example a root
filesystem, is
deferred until the next time the origin volume is activated. When
merging
starts, the resulting logical volume will have the origin's name, minor
number and UUID. While the merge is in progress, reads or
writes to
the origin appear as they were directed to the snapshot being
merged. When
the merge finishes, the merged snapshot is removed. Multiple
snapshots may
be specified on the commandline or a @tag may be used to specify
multi??? ple
snapshots be merged to their respective origin.
If you have space, I would copy your origin LV while you can. There is
nothing about cancelling the merge. I suspect you could restore the
metadata
backup from before your merge. But make backups first!
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703
591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
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/
_______________________________________________
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/
