From: Zdenek Kabelac <zkabelac@redhat.com>
To: nl6720 <nl6720@gmail.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Why isn't issue_discards enabled by default?
Date: Tue, 22 Sep 2020 12:59:55 +0200 [thread overview]
Message-ID: <8d90a730-8985-7e7d-fdcd-0db609bb36b2@redhat.com> (raw)
In-Reply-To: <5115744.4jzXO94mnC@walnut>
Dne 22. 09. 20 v 12:38 nl6720 napsal(a):
> On Tuesday, 22 September 2020 13:15:19 EEST Zdenek Kabelac wrote:
>> Dne 22. 09. 20 v 11:14 nl6720 napsal(a):
>>> On Monday, 21 September 2020 21:51:39 EEST Zdenek Kabelac wrote:
>>>> Dne 21. 09. 20 v 16:14 nl6720 napsal(a):
>>>>> Hi,
>> thin-pool is using LVs - so this is again about handling the discard
>> on a _tdata LV and it is completely unrelated to issue_discards
>> setting.
>
> from lvmthin(7):
> "passdown: Process discards in the thin pool (as with nopassdown), and
> pass the discards down the the underlying device. This is the default
> mode."
>
> It's the "underlying device" that's confusing me.
All it means is - _tdata LV is placed on some PV/device.
So the passdown means - TRIM goes through thinLV to thin-pool and then through
its _tdata LV it lands on 'underlying device' aka PV used for this LV.
If there is better and less confusing way how to describe this case,
feel free to submit better wording.
Zdenek
prev parent reply other threads:[~2020-09-22 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 14:14 [linux-lvm] Why isn't issue_discards enabled by default? nl6720
2020-09-21 14:26 ` Mark Mielke
2020-09-22 8:13 ` Zdenek Kabelac
2020-09-21 18:51 ` Zdenek Kabelac
2020-09-22 9:14 ` nl6720
2020-09-22 9:20 ` nl6720
2020-09-22 10:15 ` Zdenek Kabelac
2020-09-22 10:38 ` nl6720
2020-09-22 10:59 ` Zdenek Kabelac [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=8d90a730-8985-7e7d-fdcd-0db609bb36b2@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=nl6720@gmail.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).