From: snitzer@sourceware.org <snitzer@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/lib/activate dev_manager.c
Date: 13 Jan 2010 01:44:37 -0000 [thread overview]
Message-ID: <20100113014437.6963.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: snitzer at sourceware.org 2010-01-13 01:44:37
Modified files:
lib/activate : dev_manager.c
Log message:
Merging device is loaded with "-cow" suffix and with base name of the
origin. This is needed so that "-cow" device can be found and removed
when lvremove is performed.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/activate/dev_manager.c.diff?cvsroot=lvm2&r1=1.169&r2=1.170
--- LVM2/lib/activate/dev_manager.c 2010/01/13 01:43:32 1.169
+++ LVM2/lib/activate/dev_manager.c 2010/01/13 01:44:37 1.170
@@ -1062,16 +1062,28 @@
struct lv_segment *seg;
struct lv_layer *lvlayer;
struct dm_tree_node *dnode;
- char *name, *dlid;
+ char *name, *dlid, *lv_name;
uint32_t max_stripe_size = UINT32_C(0);
uint32_t read_ahead = lv->read_ahead;
uint32_t read_ahead_flags = UINT32_C(0);
uint16_t udev_flags = 0;
- if (lv_is_cow(lv) && find_cow(lv)->status & SNAPSHOT_MERGE && !layer)
- return 1;
+ lv_name = lv->name;
+ if (lv_is_cow(lv) && find_cow(lv)->status & SNAPSHOT_MERGE) {
+ if (layer) {
+ /*
+ * use origin's name as basis for snapshot-merge device names;
+ * this allows _clean_tree to automatically cleanup "-cow"
+ * when the origin is resumed (after merge completes)
+ */
+ lv_name = origin_from_cow(lv)->name;
+ } else {
+ /* top-level snapshot device is not needed during merge */
+ return 1;
+ }
+ }
- if (!(name = build_dm_name(dm->mem, lv->vg->name, lv->name, layer)))
+ if (!(name = build_dm_name(dm->mem, lv->vg->name, lv_name, layer)))
return_0;
if (!(dlid = build_dlid(dm, lv->lvid.s, layer)))
@@ -1084,7 +1096,7 @@
if (!(lvlayer = dm_pool_alloc(dm->mem, sizeof(*lvlayer)))) {
log_error("_add_new_lv_to_dtree: pool alloc failed for %s %s.",
- lv->name, layer);
+ lv_name, layer);
return 0;
}
next reply other threads:[~2010-01-13 1:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 1:44 snitzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 17:59 LVM2/lib/activate dev_manager.c jbrassow
2012-01-25 11:10 agk
2012-01-19 15:19 zkabelac
2011-12-21 12:55 zkabelac
2011-11-15 17:25 zkabelac
2011-11-15 17:21 zkabelac
2011-11-15 17:15 zkabelac
2011-10-28 20:34 zkabelac
2011-10-11 10:02 zkabelac
2011-10-11 9:03 zkabelac
2011-10-11 9:02 zkabelac
2011-10-11 9:01 zkabelac
2011-10-11 8:54 zkabelac
2011-10-03 18:24 zkabelac
2011-07-05 1:01 agk
2011-07-04 14:56 agk
2010-12-22 15:32 zkabelac
2010-12-20 14:04 zkabelac
2010-05-14 12:39 mbroz
2010-05-14 12:30 mbroz
2010-05-14 12:03 mbroz
2010-02-23 15:49 mornfall
2010-02-10 14:38 snitzer
2010-01-22 13:28 snitzer
2009-12-03 10:01 zkabelac
2009-12-03 9:59 zkabelac
2009-11-04 14:56 mbroz
2009-05-07 12:01 mbroz
2008-09-19 7:05 agk
2008-01-08 16:47 zkabelac
2007-12-03 18:00 agk
2007-11-29 15:04 agk
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=20100113014437.6963.qmail@sourceware.org \
--to=snitzer@sourceware.org \
--cc=lvm-devel@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.