pecific method though.


> > The other trim destroys all the data on that partition.
>
> Not always. It sends TRIM subcommand.
>

True. While technically the contents are allowed to be the same, often
times they are not... Hence the warning... and even if they are the same
right now, there's no guarantee they will remain the same in the future...

Warner

--0000000000005c82cd06178e5efc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 3, 2024 at 9:16=E2=80=AFA=
M Antony Uspensky &lt;<a href=3D"mailto:uspensky@x-art.ru">uspensky@x-art.r=
u</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>On Fri, 3 May 2024, Warner Losh wrote:<br>
<br>
&gt; Ah yes. You need to enable ZFS trim.<br>
<br>
Do you mean autotrim property? No, better to run zpool trim manually.<br></=
blockquote><div><br></div><div>It depends on the drives... But with cheap, =
crappy consumer drives, you&#39;re correct.</div><div><br></div><div>I mean=
t that you had to do it via zpool, not any specific method though.<br></div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt; The other trim destroys all the data on that partition.<br>
<br>
Not always. It sends TRIM subcommand.<br></blockquote><div><br></div><div>T=
rue. While technically the contents are allowed to be the same, often times=
 they are not... Hence the warning... and even if they are the same right n=
ow, there&#39;s no guarantee they will remain the same in the future... <br=
></div><div><br></div><div>Warner<br></div></div></div>

--0000000000005c82cd06178e5efc--