On Tue, Nov 29, 2016 at 03:21:36PM -0700, Chris Murphy wrote: > Reading the documentation for both, they're functionally the same > thing in that with these options the particular layer will pass on a > trim to the next layer underneath it. discard/fstrim/blkdiscard works fine with issue_discards=0. If it doesn't work, setting issue_discards=1 won't do a thing for you. That flag only affects the lvm tool itself, discard freed LVM extents after lvreduce or pvmove. Can't undo botched resizes anymore, too bad. Most storage layers simply don't have any setting for this at all. It just works. Or it does not (in many cases, old/stable kernel/distro). cryptsetup's allow-discards is the exception, the one layer where you have to manually enable something to make it work. Regards Andreas Klauer -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
