Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Nov 2022 14:01:58 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Wojciech Puchar <wojtek@puchar.net>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: SSD - trim fails
Message-ID:  <CANCZdfpWJude0-q=z2ZVFPuDv81p6dxd1Uo4115%2B6an9q_-f9A@mail.gmail.com>
In-Reply-To: <16589dc-a890-579-c523-db92be5335ce@puchar.net>
References:  <8a5a1943-6b3-92fd-17c-473c5b13436@puchar.net> <CANCZdfrzu_mVFN=PHLrK9dHTb5ve7H=HN9bnRf9A1JHP4P4i3Q@mail.gmail.com> <16589dc-a890-579-c523-db92be5335ce@puchar.net>

next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000095693605ece7bc26
Content-Type: text/plain; charset="UTF-8"

On Sun, Nov 6, 2022 at 3:44 PM Wojciech Puchar <wojtek@puchar.net> wrote:

> > Next, maybe the drive is lying the size of the DSM it will support, but
> again, this is a weird
> > message to report a request that's too long with.
> >
> > Maybe it doesn't support queued DSM, despite all appearances to the
> contrary from its
> > identify tables. Try setting the trem method to DSM_TRIM:
> > # sysctl kern.cam.ada.0.delete_method=DSM_TRIM
> > should do the trick. At the very least, that will change the command we
> send so if it can't
>
>
> this works. but not from /boot/loader.conf
> i put it in /etc/rc at beginning so it for sure is done before doing first
> trim.
>

Can you file a bug for this?

Also, I'm thinking that maybe this should be the default for these drives,
so if you could
send me a camcontrol identify for  it?

Warner

--00000000000095693605ece7bc26
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 Sun, Nov 6, 2022 at 3:44 PM Wojcie=
ch Puchar &lt;<a href=3D"mailto:wojtek@puchar.net">wojtek@puchar.net</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">&gt; Ne=
xt, maybe the drive is lying the size of the DSM it will support, but again=
, this is a weird<br>
&gt; message to report a request that&#39;s too long with.<br>
&gt; <br>
&gt; Maybe it doesn&#39;t support queued DSM, despite all appearances to th=
e contrary from its<br>
&gt; identify tables. Try setting the trem method to DSM_TRIM:<br>
&gt; # sysctl kern.cam.ada.0.delete_method=3DDSM_TRIM<br>
&gt; should do the trick. At the very least, that will change the command w=
e send so if it can&#39;t<br>
<br>
<br>
this works. but not from /boot/loader.conf<br>
i put it in /etc/rc at beginning so it for sure is done before doing first =
<br>
trim.<br></blockquote><div><br></div><div>Can you file a bug for this?</div=
><div><br></div><div>Also, I&#39;m thinking that maybe this should be the d=
efault for these drives, so if you could</div><div>send me a camcontrol ide=
ntify for=C2=A0 it?</div><div><br></div><div>Warner=C2=A0</div></div></div>

--00000000000095693605ece7bc26--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpWJude0-q=z2ZVFPuDv81p6dxd1Uo4115%2B6an9q_-f9A>