All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0 of 13] LVM add 'mirrored' log type
Date: Mon, 22 Feb 2010 04:18:35 -0500	[thread overview]
Message-ID: <4B824BEB.60708@redhat.com> (raw)
In-Reply-To: <B66E0CF9-8028-4597-AE6E-3B2F1A7B213A@redhat.com>

Jonathan Brassow wrote:
> I'm also testing the other approach; that is, allowing lvconvert to take
> non-top-level LVs (e.g. "lv_mlog").  It seems to work just fine.  We
> might want to strongly consider allowing this.
> 
> There are drawbacks to this approach too, however.  For example, when
> one of the devices of the log fails, it will be treated as an 'image'
> failure, and not a 'log' failure (I can fix that though by checking its
> lv->status).  If we decide to go this route, we will have to decide if
> this is the behavior we want or not.  (Once the log is linear, it will
> behave as you would expect - either being replaced or removed according
> to the log policy.)

This approach requires two threads in dmeventd; it is for a top-level LV,
and another is for a mirrored log. If a leg and mirrored log failed at
the same time, a mirrored log needs to be recovered before a top-level LV.
I think this approach is also good if we can handle this situation.

Thanks,
Taka





  reply	other threads:[~2010-02-22  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 17:55 [PATCH 0 of 13] LVM add 'mirrored' log type Jonathan Brassow
2010-02-18 16:48 ` Jonathan Brassow
2010-02-22  9:18   ` Takahiro Yasui [this message]
2010-02-22  9:09 ` Takahiro Yasui
  -- strict thread matches above, loose matches on Subject: below --
2010-02-17 17:53 Jonathan Brassow

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=4B824BEB.60708@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.