summaryrefslogtreecommitdiff
path: root/lib/snapshot
diff options
context:
space:
mode:
authorZdenek Kabelac <zkabelac@redhat.com>2014-02-27 12:55:50 +0100
committerZdenek Kabelac <zkabelac@redhat.com>2014-02-27 13:00:49 +0100
commitd00fc1de784cee27d6ddb1b045a67c930f743074 (patch)
treeb134c8b8d6b60f2aaca7a15181cbb2c10c282818 /lib/snapshot
parent1769eddde7dcdd16716d646e14487cc1df6a3efc (diff)
downloadlvm2-d00fc1de784cee27d6ddb1b045a67c930f743074.tar.gz
snapshot: correct previous snapshot commit
Condition was swapped - however since it's been based on 'random' memory content it's been missed as attribute has not been set. So now we have quite a few possible results when testing. We have old status without separate metadata and we have kernels with fixed snapshot leak bug. (in-release update)
Diffstat (limited to 'lib/snapshot')
-rw-r--r--lib/snapshot/snapshot.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/lib/snapshot/snapshot.c b/lib/snapshot/snapshot.c
index 0b7b84568..64919b0f3 100644
--- a/lib/snapshot/snapshot.c
+++ b/lib/snapshot/snapshot.c
@@ -165,6 +165,9 @@ static int _snap_target_present(struct cmd_context *cmd,
log_very_verbose("Target snapshot may leak metadata.");
}
+ if (attributes)
+ *attributes = _snap_attrs;
+
/* TODO: test everything at once */
if (seg && (seg->status & MERGING)) {
if (!_snap_merge_checked) {