public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/lib/metadata thin_manip.c Date: Wed, 19 Oct 2011 16:37:00 -0000 [thread overview] Message-ID: <20111019163731.4586.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-10-19 16:37:30 Modified files: lib/metadata : thin_manip.c Log message: Drop messages referencing deleted LV lvremove may remove problematic LV for thin target. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/thin_manip.c.diff?cvsroot=lvm2&r1=1.9&r2=1.10 --- LVM2/lib/metadata/thin_manip.c 2011/10/19 16:36:40 1.9 +++ LVM2/lib/metadata/thin_manip.c 2011/10/19 16:37:30 1.10 @@ -46,12 +46,32 @@ int detach_pool_lv(struct lv_segment *seg) { + struct lv_thin_message *tmsg; + struct dm_list *l, *lt; + if (!lv_is_thin_pool(seg->pool_lv)) { log_error(INTERNAL_ERROR "LV %s is not a thin pool", seg->pool_lv->name); return 0; } + /* Drop any message referencing removed segment */ + dm_list_iterate_safe(l, lt, &first_seg(seg->pool_lv)->thin_messages) { + tmsg = dm_list_item(l, struct lv_thin_message); + switch (tmsg->type) { + case DM_THIN_MESSAGE_CREATE_SNAP: + case DM_THIN_MESSAGE_CREATE_THIN: + case DM_THIN_MESSAGE_TRIM: + if (first_seg(tmsg->u.lv) == seg) { + log_debug("Discarding message for LV %s.", + tmsg->u.lv->name); + dm_list_del(&tmsg->list); + } + default: + break; + } + } + if (!attach_pool_message(first_seg(seg->pool_lv), DM_THIN_MESSAGE_DELETE, NULL, seg->device_id, 0))
next reply other threads:[~2011-10-19 16:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-19 16:37 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-02-12 21:42 agk 2012-01-25 9:17 zkabelac 2011-12-10 0:47 agk 2011-11-07 11:04 zkabelac 2011-11-07 10:59 zkabelac 2011-11-03 15:58 zkabelac 2011-10-19 16:32 zkabelac 2011-10-03 19:10 zkabelac
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=20111019163731.4586.qmail@sourceware.org \ --to=zkabelac@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).