linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: Kumar amit mehta <gmate.amit@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvcreate --thin gives "unknown segment type" error
Date: Mon, 22 Jul 2013 22:18:48 +0200	[thread overview]
Message-ID: <51ED93A8.6040303@redhat.com> (raw)
In-Reply-To: <20130722112348.GB1570@gmail.com>

Dne 22.7.2013 13:23, Kumar amit mehta napsal(a):
> On Mon, Jul 22, 2013 at 06:57:42AM -0400, Kumar amit mehta wrote:
>> On Mon, Jul 22, 2013 at 02:15:36PM +0200, Zdenek Kabelac wrote:
>>> configure --with-thin=internal
>>>
>>> (and you will likely miss  '--enable-udev_sync'
>> Thank you, it worked!
>>
>> However, It seems that "discards" behavior for thin pool is not
>> supported on RHEL 6.4. Please confirm.
>> # ./configure --with-thin=internal --enable-debug
>>
>> # make; make install
>>
>> # lvcreate --discards passdown -L 1G -T thinvg1/thinlv1
>>    Logical volume "thinlv1" created
>>
>> # lvs -o +devices|grep -i thinlv1
>>    thinlv1       thinvg1       twi-a-tz-   1.00g               0.00
>> thinlv1_tdata(0)
>>
>> # dmesg
>> device-mapper: thin: Data device (dm-3) discard unsupported: Disabling
>> discard passdown.
>>

It's your backend device used for thinpool data  which doesn't support 
discard. So it fallbacks to  nopassdown behaviour (discard is processed only 
at pool level).


> I'm invoking these commands on a VM. I do not know, from where these
> storage were mapped to my VM(were done my some storage admin). However

Important piece of puzzle - if you want to see TRIM command hits your storage,
your storage needs to support it ;)

BTW it's perfectly ok to use thin pool only with nopassdown.

Zdenek


NOTE: issue_discard in lvm.conf is not related in any way with --discards 
option for thin pool creation.

  reply	other threads:[~2013-07-22 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  5:15 [linux-lvm] lvcreate --thin gives "unknown segment type" error Kumar amit mehta
2013-07-22 12:15 ` Zdenek Kabelac
2013-07-22 10:57   ` Kumar amit mehta
2013-07-22 11:23     ` Kumar amit mehta
2013-07-22 20:18       ` Zdenek Kabelac [this message]
2013-07-23  0:52         ` Kumar amit mehta

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=51ED93A8.6040303@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=gmate.amit@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).