02.12.2019 20:35, Andriy Gapon wrote:
> On 02/12/2019 11:27, Scott Bennett wrote:
>> The vast majority of my "destroy" operations are for
snapshots, but what
>> I have seen is that, without the "-d", the command does not
return until the
>> disk activity of the "destroy" finishes, but with the
"-d", it returns within
>> a couple of seconds,--i.e., just long enough to get the operation
going--and
>> the disk I/Os continue until the work is done and free space in the
pool increases
>> until the I/Os stop.
>> Perhaps the man pages for zfs(8) and zpool-features(7) need some
modification/
>> clarification on this matter.
>
> I don't know how to explain what you see, but the manual pages are
correct.
> -d has nothing to do with asynchronous destroy which is automatic (when
enabled).
It seems that "zfs destroy" writes and/or removes large enough amount
of data to spend lots of time
before return when TRIM performance is bad.