From: Takahiro Yasui <tyasui@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Ignore _mlog name restriction for lvconvert repair
Date: Thu, 11 Feb 2010 14:55:05 -0500 [thread overview]
Message-ID: <4B746099.7010709@redhat.com> (raw)
In-Reply-To: <471e224a57131c07b705.1265821968@localhost>
Malahal Naineni wrote:
> lvconvert --repair is done on _mlog mirrored log logical volumes from
> dmeventd if something fails.
>
> diff -r 86200db56a7c -r 471e224a5713 tools/lvconvert.c
> --- a/tools/lvconvert.c Tue Feb 09 17:49:50 2010 -0800
> +++ b/tools/lvconvert.c Wed Feb 10 09:12:11 2010 -0800
> @@ -105,8 +105,12 @@ static int _lvconvert_name_params(struct
> if ((ptr = strrchr(lp->lv_name_full, '/')))
> lp->lv_name = ptr + 1;
>
> - if (!apply_lvname_restrictions(lp->lv_name))
> - return_0;
> + /* _mlog is an internal name, but it could be mirrored, so
> + * allow repairing it.
> + */
> + if (!arg_count(cmd, repair_ARG) || !strstr(lp->lv_name, "_mlog"))
> + if (!apply_lvname_restrictions(lp->lv_name))
> + return_0;
>
> if (*pargc && lp->snapshot) {
> log_error("Too many arguments provided for snapshots");
lvname is better to be checked if a logical volume is not mirrored log
but simple logical volume. How about using (lv->status & MIRRORED) for
the check?
Thanks,
Taka
next prev parent reply other threads:[~2010-02-11 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 17:12 [PATCH] Ignore _mlog name restriction for lvconvert repair Malahal Naineni
2010-02-11 19:55 ` Takahiro Yasui [this message]
2010-02-11 20:38 ` malahal
2010-02-12 1:14 ` Takahiro Yasui
2010-02-12 21:30 ` Jonathan Brassow
2010-02-12 21:45 ` Jonathan Brassow
2010-02-12 22:14 ` Takahiro Yasui
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=4B746099.7010709@redhat.com \
--to=tyasui@redhat.com \
--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.