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: Tue, 10 Feb 2009 22:26:58 -0500	[thread overview]
Message-ID: <49924582.3040708@redhat.com> (raw)

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.

# /sbin/dmsetup ls --tree
vg--mirror-mirror (253:6)
 ??vg--mirror-mirror_mimage_1 (253:5)
 ?  ?? (8:80)
 ??vg--mirror-mirror_mimage_0 (253:4)
 ?  ?? (8:64)
 ??vg--mirror-mirror_mlog (253:3)
    ??vg--log-mirror--log (253:2)
       ??vg--log-mirror--log_mimage_1 (253:1)
       ?  ?? (8:32)
       ??vg--log-mirror--log_mimage_0 (253:0)
          ?? (8:48)

# vgs
  Found duplicate PV DoSlX0JCU3qxxN4UVqgtqvzP1crZAwom: using \
  /dev/mapper/vg--log-mirror--log_mimage_1 not \
  /dev/mapper/vg--log-mirror--log_mimage_0
  Found duplicate PV DoSlX0JCU3qxxN4UVqgtqvzP1crZAwom: using \
  /dev/vg-log/mirror-log not /dev/mapper/vg--log-mirror--log_mimage_1
  VG        #PV #LV #SN Attr   VSize  VFree
  vg-log      2   1   0 wz--n- 31.99G 31.97G
  vg-mirror   3   1   0 wz--n- 32.00G 31.97G

This warning message is displayed during scan of PVs because the
following three logical volumes have the same UUID.

    /dev/vg-log/mirror-log
    /dev/mapper/vg--log-mirror--log_mimage_0
    /dev/mapper/vg--log-mirror--log_mimage_1

And this warning can be avoided by setting filter in config file, but
I hope that these warnings are not displayed without a config setting.

    filter = [ ..., "r|.*_mimage_.$|", ... ]

Do you think it is reasonable idea to skip device scan of LVs which have
a string, "_mimage_", in their name? I think that adding a static filter
for "_mimage_" in lvm commands is one of the solutions.

I appreciate your kind comments to fix this issue.

Thanks,
---
Takahiro Yasui
Hitachi Computer Products (America), Inc.



             reply	other threads:[~2009-02-11  3:26 UTC|newest]

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