Dne 21. 09. 20 v 16:14 nl6720 napsal(a):
Hi,
I wanted to know why the "issue_discards" setting isn't enabled by
default. Are there any dangers in enabling it or if not is there a
chance of getting the default changed?
Also it's not entirely clear to me if/how "issue_discards" affects thin
pool discard passdown.
Hi
Have you checked it's enclosed documentation in within /etc/lvm/lvm.conf ?
issue_discards is PURELY & ONLY related to sending discard to removed disk
extents/areas after 'lvremove'.
It is't not in ANY way related to actual discard handling of the LV itself. So
if you have LV on SSD it is automatically processing discards. From the same
reason it's unrelated to discard processing of thin-pools.
And finally why we prefer issue_discards to be disabled (=0) by default. It's
very simple - with lvm2 we try (when we can) to support one-command-back
restore - so if you do 'lvremove' - you can use vgcfgrestore to restore
previous metadata and you have your LV back with all the data inside.
When you have issue_discards=1 - the device gets TRIM - so all the data
are discarded at device level - so when you try to restore your
previous metadata - well it's nice - but content is gone forever....
If user can live with this 'risk' and prefers immediate discard - perfectly
fine - but it should be (IMHO) admin's decision.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
