All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 2 of 2] [RFC] handle a temporary secondary mirror device failure
Date: Wed, 02 Dec 2009 19:00:21 -0500	[thread overview]
Message-ID: <4B16FF95.6010603@redhat.com> (raw)
In-Reply-To: <a0324c61e9fc527d6a9d.1259576550@localhost>

On 11/30/09 05:22, Malahal Naineni wrote:
> If "retry" policy is selected, then the mirror DSO uses "dmsetup"
> command to restart a resync. Right now, it is done immediately but we
> should do it after a configured time. Also, this is done endlessly but
> should be done only few configured times.

It sounds good to me. This feature would work in a variety of
environments by adding configurable parameter as you mentioned.

> Calling 'lvchange --refresh' to re-integrate the secondary mirror upon a
> leg failure works if there are no device failures while the "lvchange"
> is running.  Otherwise, the failed device is replaced with "error"
> target which is not what we want. For now, this patch calls "dmsetup",
> but should be replaced with a suitable "LVM" command.

> +	snprintf(cmd_str, CMD_SIZE, "dmsetup suspend %s-%s", vg, lv);
> +	syslog(LOG_ERR, "Running command: %s", cmd_str);

We need to re-queue blocked I/Os instead of finishing them by -EIO.
I think that "--noflush" option is necessary for "dmsetup suspend."

Thanks,
Taka



  reply	other threads:[~2009-12-03  0:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 10:22 [PATCH 0 of 2] imporoved mirror DSO logging Malahal Naineni
2009-11-30 10:22 ` Malahal Naineni
2009-11-30 10:22 ` [PATCH 1 of 2] Improve mirror DSO's failure logging Malahal Naineni
2009-11-30 10:22   ` Malahal Naineni
2009-11-30 10:22 ` [PATCH 2 of 2] [RFC] handle a temporary secondary mirror device failure Malahal Naineni
2009-11-30 10:22   ` Malahal Naineni
2009-12-03  0:00   ` Takahiro Yasui [this message]
2009-12-03  2:36     ` malahal
2009-12-08 21:12       ` 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=4B16FF95.6010603@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.