From: Lakshmi Narasimhan Sundararajan <lsundararajan@purestorage.com>
To: lvm-devel@lists.linux.dev
Subject: Reg thin pool and discard handling
Date: Thu, 11 Jan 2024 09:11:44 +0530 [thread overview]
Message-ID: <CAFe+wq3F1TCe9c6VXXiHFcA2Fys_L6+0Jv8FmDy8aH-0HfsOqw@mail.gmail.com> (raw)
Hi Team,
A very happy new year to you all.
When a thin pool is created it has option to control discard behavior.
Typically the useful ones are either discard_passdown vs no_discard_passdown.
My question is as below:
If the thin pool is in "no_discard_passdown" and later changes to
"discard_passdown", would there be a way to reinitiate discard for
those ranges that was not passed down?
Typically fs sitting on top of the thin lv controls discard ranges and
that was already handled as "no_discard_passdown".
Later if say, the backing storage gets filled up, then how can one
re-initiate discard again to allow it to reach
backing storage?
Thanks for your pointers.
Best regards
next reply other threads:[~2024-01-11 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 3:41 Lakshmi Narasimhan Sundararajan [this message]
2024-01-12 10:45 ` Reg thin pool and discard handling Zdenek Kabelac
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=CAFe+wq3F1TCe9c6VXXiHFcA2Fys_L6+0Jv8FmDy8aH-0HfsOqw@mail.gmail.com \
--to=lsundararajan@purestorage.com \
--cc=lvm-devel@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).