All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: vaLentin chernoZemski <valentin@siteground.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvremove does not pass discards if volume is part of thin pool
Date: Wed, 12 Aug 2015 09:57:23 +0200	[thread overview]
Message-ID: <55CAFC63.6070409@redhat.com> (raw)
In-Reply-To: <55CAF9DD.3090707@redhat.com>

On 08/12/2015 09:46 AM, Peter Rajnoha wrote:
> On 08/11/2015 04:35 PM, Mike Snitzer wrote:
>> I'll have to defer to the lvm2 developers, I thought we added explicit
>> logging when lvm2 issues discards (as part of lvremove, etc) -- Peter,
>> and/or Alasdair?
>>
> 
> Yes, we log that like (visible in the verbose -vvv output):
> 
>   "Discarding X extents offset Y sectors on /dev/Z."
> 
> Also, when removing a volume, we issue this message:
> 
> # lvremove vg1/lvol0
> Do you really want to remove and DISCARD logical volume lvol0? [y/n]: 
> 
> For this, the "devices/issue_discards=1" must be set - it's not
> by default.
> 

Well, sorry, this applies for usual PVs, not thin pools (I overlooked
the $subject and just saw the last question...)

-- 
Peter

  reply	other threads:[~2015-08-12  7:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  8:56 [linux-lvm] lvremove does not pass discards if volume is part of thin pool vaLentin chernoZemski
2015-08-10 17:49 ` Mike Snitzer
2015-08-11  8:07   ` vaLentin chernoZemski
2015-08-11 14:35     ` Mike Snitzer
2015-08-11 14:56       ` vaLentin chernoZemski
2015-08-12  7:46       ` Peter Rajnoha
2015-08-12  7:57         ` Peter Rajnoha [this message]
2015-08-19 10:40       ` vaLentin chernoZemski
2016-01-22 17:18         ` Tomas Janousek
2016-01-26 17:03           ` Tomas Janousek

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=55CAFC63.6070409@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=valentin@siteground.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.