From: Rahul Hinduja <rhinduja@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Issue in creating thinpool when used different pool metadatasize
Date: Wed, 16 Apr 2014 09:31:47 -0400 (EDT) [thread overview]
Message-ID: <494273392.10071876.1397655107769.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1326353213.10069520.1397654927537.JavaMail.zimbra@redhat.com>
----- Original Message -----
> From: "Rahul Hinduja" <rhinduja@redhat.com>
> To: linux-lvm@redhat.com
> Sent: Wednesday, April 16, 2014 6:58:47 PM
> Subject: Issue in creating thinpool when used different pool metadatasize
>
> Hello All,
>
> This might be some basic mistake I would be doing with respect to different
> poolmetadata size.
>
> When I am trying to create thinpool with poolmetadatasize as 4m it fails but
> similar is successful when I try to create with 5m. Default poolmetadatasize
> can be 2m to 16g so I am not sure what is error I am enforcing it to fail.
>
> Kindly help me out with this issue.
>
>
> Case 1: poolmetadatasize as 4m
>
> #script to create thinpool with poolmetadatasize 4m
>
> [root@rahul ~]# cat temp
> pvcreate /dev/vdb
> pvcreate /dev/vdc
> pvcreate /dev/vdd
> pvcreate /dev/vde
>
> vgcreate snap_vg0 /dev/vdb /dev/vdc /dev/vdd /dev/vde
> lvcreate -L 90G --poolmetadatasize 4m -T /dev/snap_vg0/snap_thin_pool0
> #lvcreate -L 90G -T /dev/snap_vg0/snap_thin_pool0
> lvcreate -V90G -T /dev/snap_vg0/snap_thin_pool0 -n snap_thin_vol0
> [root@rahul ~]#
> [root@rahul ~]#
#Creation Fails
[root@rahul ~]# ./temp
Physical volume "/dev/vdb" successfully created
Physical volume "/dev/vdc" successfully created
Physical volume "/dev/vdd" successfully created
Physical volume "/dev/vde" successfully created
Volume group "snap_vg0" successfully created
Logical volume "lvol0" created
device-mapper: reload ioctl on failed: Invalid argument
Failed to suspend pool snap_thin_pool0.
Thin pool snap_thin_pool0 not found in Volume group snap_vg0.
[root@rahul ~]#
>
>
>
>
> Case 2: poolmetadatasize as 5m
>
> #script to create thinpool with poolmetadatasize 5m
>
> [root@rahul ~]# cat temp
> pvcreate /dev/vdb
> pvcreate /dev/vdc
> pvcreate /dev/vdd
> pvcreate /dev/vde
>
> vgcreate snap_vg0 /dev/vdb /dev/vdc /dev/vdd /dev/vde
> lvcreate -L 90G --poolmetadatasize 5m -T /dev/snap_vg0/snap_thin_pool0
> #lvcreate -L 90G -T /dev/snap_vg0/snap_thin_pool0
> lvcreate -V90G -T /dev/snap_vg0/snap_thin_pool0 -n snap_thin_vol0
> [root@rahul ~]#
> [root@rahul ~]#
>
>
>
> #Creation Success
>
> [root@rahul ~]# ./temp
> Physical volume "/dev/vdb" successfully created
> Physical volume "/dev/vdc" successfully created
> Physical volume "/dev/vdd" successfully created
> Physical volume "/dev/vde" successfully created
> Volume group "snap_vg0" successfully created
> Rounding up size to full physical extent 8.00 MiB
> Logical volume "lvol0" created
> Logical volume "snap_thin_pool0" created
> Logical volume "snap_thin_vol0" created
> [root@rahul ~]#
>
>
> Please find the attachment with detailed outputs of different lv commands
>
> Thanks,
> Rahul
prev parent reply other threads:[~2014-04-16 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <364130975.10063540.1397654548006.JavaMail.zimbra@redhat.com>
2014-04-16 13:28 ` [linux-lvm] Issue in creating thinpool when used different pool metadatasize Rahul Hinduja
2014-04-16 13:31 ` Rahul Hinduja [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=494273392.10071876.1397655107769.JavaMail.zimbra@redhat.com \
--to=rhinduja@redhat.com \
--cc=linux-lvm@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.