All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: lvm-devel@redhat.com
Subject: lvm2: warning after mirrored LV is initialized as PV
Date: Wed, 11 Feb 2009 08:32:56 -0500	[thread overview]
Message-ID: <4992D388.90405@redhat.com> (raw)
In-Reply-To: <20090211054908.GA23806@us.ibm.com>

malahal at us.ibm.com wrote:
> Takahiro Yasui [tyasui at redhat.com] wrote:
>> Jonathan Brassow wrote (in dm-devel)
>>> Note that once you get #1 done you /should/ be able to get a mirrored  
>>> log by:
>>> prompt> lvcreate -m1 --mirrorlog core -l 1 -n mirrored_log vg
>>> prompt> lvcreate -m1 -L 5G -n mirror vg /dev/sdb /dev/sdc /dev/vg/ 
>>> mirrored_log
>> I'm now evaluating the layered LV approach, which was suggested by Jon,
>> with the latest LVM command (2.02.45), but some warning messages are
>> displayed after mirrored LV was initialized as PV.
> 
> Jonathan and Alasdair explained what they mean by 'generic layering' in
> one of the DM/multipath Monday meetings.  Currently allocations are done
> from PV's. They want to include LV's in the allocation map. This
> requires changes in the allocation path. We probably want to designate
> these LVs to avoid admin mistakes. With the above changes in place, we
> don't need to include LVs as PVs at all.
>
...
> If you don't include LVs as PVs, you don't get any warnings you listed!

Thank you for the explanation. I misunderstood their comments. So in
'generic layering', LVs works like physical PVs without creating PV
from LV with pvcreate command, and we don't encounter this warning.

Thanks,
Taka



      reply	other threads:[~2009-02-11 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  3:26 lvm2: warning after mirrored LV is initialized as PV Takahiro Yasui
2009-02-11  5:49 ` malahal
2009-02-11 13:32   ` Takahiro Yasui [this message]

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=4992D388.90405@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.