All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: malahal@us.ibm.com
Cc: dm-devel@redhat.com
Subject: Re: [RFC] [PATCH] lvm2: mirroredlog support
Date: Tue, 20 Jan 2009 16:29:35 -0500	[thread overview]
Message-ID: <4976423F.2070103@redhat.com> (raw)
In-Reply-To: <20081230001055.GA13710@us.ibm.com>

malahal@us.ibm.com wrote:
> This patch adds '--mirroredlog' option to LVM commands to create a
> mirror with mirrored log device. Rebased to the latest LVM code
> (LVM2.2.02.43). Appreciate any comments.

Hi, Malahal

This is the additional test results of mirrored log. Currently your
patch is proposed by "RFC", and these might be known issues to you,
but I hope this reports would be helpful to improve your patch.
Any comments are welcome.


0. Test environment
  - LVM2.2.02.43 with mirrored log patch
  - vg00 is composed of 8 PVs (/dev/sd[c-j])


1. SIGSEGV at converting a core log to a mirrored log

  # dmsetup status
  vg00-lv00_mimage_1: 0 24576 linear
  vg00-lv00_mimage_0: 0 24576 linear
  vg00-lv00: 0 24576 mirror 2 253:3 253:4 24/24 1 AA 1 core

  # lvconvert -m1 --mirroredlog /dev/vg00/lv00
  Segmentation fault

  # lvconvert -m2 --mirroredlog /dev/vg00/lv00
  Segmentation fault


2. Fail at conversion from 2 legs to 3 legs

  lv00 in vg00 has 2 legs (2 log legs and 2 data legs), and when it is
  converted to the structure with 3 lets, the conversion fails.

  vg00-lv00 (253:5)
   + vg00-lv00_mimage_1 (253:4)
   + vg00-lv00_mimage_0 (253:3)
   + vg00-lv00_mlog (253:2)
      + vg00-lv00_mlog_mimage_1 (253:1)
      + vg00-lv00_mlog_mimage_0 (253:0)

  # lvconvert -m2 --mirroredlog /dev/vg00/lv00
    device-mapper: reload ioctl failed: No such device or address
    Failed to lock lv00
  # dmsetup status
  vg00-lv00_mimage_2: 0 8192 linear    <-- data leg is created
  vg00-lv00_mimage_1: 0 24576 linear
  vg00-lv00_mlog_mimage_1: 0 8192 linear
  vg00-lv00_mimage_0: 0 24576 linear
  vg00-lv00_mlog_mimage_0: 0 8192 linear
  vg00-lv00_mimagetmp_2: 0 24576 error <-- temporary data log exists
  vg00-lv00_mlog: 0 8192 mirror 2 253:1 253:2 8/8 1 AA 1 core
  vg00-lv00: 0 24576 mirror 2 253:4 253:5 24/24 1 AA 3 disk 253:3 A


3. Fail at conversion from disk log to mirrored log

  # dmsetup status
  vg00-lv00_mimage_1: 0 24576 linear
  vg00-lv00_mimage_0: 0 24576 linear
  vg00-lv00_mlog: 0 8192 linear
  vg00-lv00: 0 24576 mirror 2 253:1 253:2 24/24 1 AA 3 disk 253:0 A

  # lvconvert -m1 --mirroredlog /dev/vg00/lv00
  Logical volume lv00 already has 1 mirror(s).

   => disk log should be converted to mirrored log?

  # lvconvert -m2 --mirroredlog /dev/vg00/lv00
  device-mapper: reload ioctl failed: No such device or address
  Failed to lock lv00
  # dmsetup status
  vg00-lv00_mimage_2: 0 8192 linear
  vg00-lv00_mimage_1: 0 24576 linear
  vg00-lv00_mimage_0: 0 24576 linear
  vg00-lv00_mimagetmp_2: 0 24576 error
  vg00-lv00_mlog: 0 8192 linear
  vg00-lv00: 0 24576 mirror 2 253:1 253:2 24/24 1 AA 3 disk 253:0 A

   => disk log should be converted to mirrored log with 3 legs?


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

  parent reply	other threads:[~2009-01-20 21:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30  0:10 [RFC] [PATCH] lvm2: mirroredlog support malahal
2008-12-30  0:10 ` malahal
2009-01-19 22:56 ` Takahiro Yasui
2009-01-20  1:54   ` malahal
2009-01-20  7:13     ` Stefan Raspl
2009-01-20 17:38       ` malahal
2009-01-20 19:52         ` Takahiro Yasui
2009-01-20 22:12     ` Takahiro Yasui
2009-01-20 21:29 ` Takahiro Yasui [this message]
2009-01-20 22:14   ` malahal
2009-01-23 19:14 ` Jonathan Brassow
2009-01-23 21:07   ` malahal
  -- strict thread matches above, loose matches on Subject: below --
2009-09-23  3:03 malahal
2009-09-23 20:29 ` Jonathan Brassow
2009-09-23 20:44   ` malahal
2009-09-24  5:22 ` Takahiro Yasui
2009-09-30 15:50 ` Jonathan Brassow
2009-09-30 16:35   ` Alasdair G Kergon
2009-09-30 19:48     ` Jonathan Brassow
2009-09-30 21:18       ` Alasdair G Kergon
2009-09-30 21:46         ` Alasdair G Kergon
2009-09-30 21:19       ` malahal
2009-10-01  0:13   ` malahal

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=4976423F.2070103@redhat.com \
    --to=tyasui@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=malahal@us.ibm.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.