From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Patrick Dung <mpatdung@gmail.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Is trim/discard supported on LVM RAID logical volume?
Date: Tue, 29 Nov 2016 23:09:49 +0100 [thread overview]
Message-ID: <20161129220949.GA4035@metamorpher.de> (raw)
In-Reply-To: <CAJCQCtSpOfMvgfxOFvQtM=zcOnyoqvu3GregmW9NS5j9auRuyw@mail.gmail.com>
On Tue, Nov 29, 2016 at 01:20:16PM -0700, Chris Murphy wrote:
> Seen /etc/lvm/lvm.conf issue_discards is probably set to 0.
It should be 0 unless you understand what it's doing and actually want it...
Don't confuse LVM's issue_discards with cryptsetup's allow_discards.
Regards
Andreas Klauer
next prev parent reply other threads:[~2016-11-29 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 12:59 Is trim/discard supported on LVM RAID logical volume? Patrick Dung
2016-11-29 20:20 ` Chris Murphy
2016-11-29 22:09 ` Andreas Klauer [this message]
2016-11-29 22:21 ` Chris Murphy
2016-11-29 23:32 ` Andreas Klauer
2016-11-30 8:25 ` Patrick Dung
2016-11-30 16:18 ` Phil Turmel
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=20161129220949.GA4035@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mpatdung@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).