public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kurt Miller <kurt@intricatesoftware.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: LSI SAS2008 SATA TRIM not working
Date: Fri, 07 Feb 2014 15:52:43 -0500	[thread overview]
Message-ID: <1391806363.2761.8.camel@sonic.justonedata.com> (raw)
In-Reply-To: <yq1vbwqslek.fsf@sermon.lab.mkp.net>

On Fri, 2014-02-07 at 15:44 -0500, Martin K. Petersen wrote:
> >>>>> "Kurt" == Kurt Miller <kurt@intricatesoftware.com> writes:
> 
> Kurt> Is TRIM working for anyone using LSI SAS2008 controllers?
> 
> Yes. But its SAT appears to be somewhat selective about which devices it
> flags as capable.
> 
> Please send me the output of:
> 
> # sg_readcap -l /dev/sdc
> # sg_vpd -p bl /dev/sdc
> # sg_vpd -p lbpv /dev/sdc
> 

Hi Martin,

Thank you for your reply. Below is the output you requested. Note that
when the EVO's are connected to a SATA AHCI port on my desktop
motherboard, TRIM works okay. Please let me know if you need additional
information.

Regards,
-Kurt

# sg_readcap -l /dev/sdc
Read Capacity results:
   Protection: prot_en=0, p_type=0, p_i_exponent=0
   Logical block provisioning: lbpme=0, lbprz=0
   Last logical block address=976773167 (0x3a38602f), Number of logical
blocks=976773168
   Logical block length=512 bytes
   Logical blocks per physical block exponent=0
   Lowest aligned logical block address=0
Hence:
   Device size: 500107862016 bytes, 476940.0 MiB, 500.11 GB

# sg_vpd -p bl /dev/sdc
Block limits VPD page (SBC):
  Write same no zero (WSNZ): 0
  Maximum compare and write length: 0 blocks
  Optimal transfer length granularity: 0 blocks
  Maximum transfer length: 0 blocks
  Optimal transfer length: 0 blocks
  Maximum prefetch length: 0 blocks
  Maximum unmap LBA count: 0
  Maximum unmap block descriptor count: 0
  Optimal unmap granularity: 0
  Unmap granularity alignment valid: 0
  Unmap granularity alignment: 0
  Maximum write same length: 0x0 blocks

# sg_vpd -p lbpv /dev/sdc
Logical block provisioning VPD page (SBC):
  Unmap command supported (LBPU): 0
  Write same (16) with unmap bit supported (LBWS): 0
  Write same (10) with unmap bit supported (LBWS10): 0
  Logical block provisioning read zeros (LBPRZ): 0
  Anchored LBAs supported (ANC_SUP): 0
  Threshold exponent: 0
  Descriptor present (DP): 0
  Provisioning type: 0



  reply	other threads:[~2014-02-07 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 23:56 LSI SAS2008 SATA TRIM not working Kurt Miller
2014-02-07 20:44 ` Martin K. Petersen
2014-02-07 20:52   ` Kurt Miller [this message]
2014-02-07 20:59     ` Martin K. Petersen
2014-02-07 21:24       ` Kurt Miller
2014-02-08  1:24         ` Martin K. Petersen
2014-02-09 22:28           ` Kurt Miller
2014-02-12  2:27             ` Kurt Miller
2014-04-11 16:57               ` LSI SAS - SSDs with DRAT and DZAT Bernd Schubert
2014-04-17 19:42                 ` Martin K. Petersen
2014-04-17 22:32                   ` Kurt Miller
     [not found]                     ` <CAN7X1Un4=dTyvRbyt=0j6Q+=OBcXRDB+0J+dLPZCboKdxyTTzQ@mail.gmail.com>
2014-04-18 15:23                       ` Kurt Miller
2014-02-07 20:46 ` LSI SAS2008 SATA TRIM not working Kurt Miller
2015-09-09  1:45   ` Chang Limin

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=1391806363.2761.8.camel@sonic.justonedata.com \
    --to=kurt@intricatesoftware.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /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