public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sven Hugi <hugi.sven@gmail.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: Re: Samsung t5 / t3 problem with ncq trim
Date: Thu, 20 Jan 2022 21:14:57 -0500	[thread overview]
Message-ID: <yq1wnithm6g.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAFrqyV4n8r6TwNsETfVTv+F_nn8Hg=HuZ6OHgmG_HxPVcvfPzA@mail.gmail.com> (Sven Hugi's message of "Thu, 20 Jan 2022 16:42:37 +0100")


Sven,

>  -> sudo sg_readcap -l sda
> Read Capacity results:
>    Protection: prot_en=0, p_type=0, p_i_exponent=0
>    Logical block provisioning: lbpme=0, lbprz=0
>    Last LBA=976773167 (0x3a38602f), Number of logical blocks=976773168
>    Logical block length=512 bytes

> lbpme=0...
> so, i guess it's not because of trim...

Correct, Linux wouldn't be sending trims to that drive.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2022-01-21  2:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 15:22 Samsung t5 / t3 problem with ncq trim Sven Hugi
2022-01-19  3:20 ` Martin K. Petersen
2022-01-19 16:06   ` Sven Hugi
2022-01-19 16:31     ` Martin K. Petersen
2022-01-19 18:59       ` Sven Hugi
2022-01-19 22:38         ` Martin K. Petersen
2022-01-19 23:02           ` Sven Hugi
2022-01-20 15:42             ` Sven Hugi
2022-01-21  2:14               ` Martin K. Petersen [this message]
2022-01-21 17:23                 ` Sven Hugi
2022-01-22  1:05                   ` Damien Le Moal
2022-02-23  8:19                     ` Sven Hugi

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=yq1wnithm6g.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=hugi.sven@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    /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