From: Chang Limin <changlimin@h3c.com>
To: linux-scsi@vger.kernel.org
Subject: Re: LSI SAS2008 SATA TRIM not working
Date: Wed, 9 Sep 2015 01:45:57 +0000 (UTC) [thread overview]
Message-ID: <loom.20150909T034002-827@post.gmane.org> (raw)
In-Reply-To: 1391805990.2761.4.camel@sonic.justonedata.com
Kurt Miller <kurt <at> intricatesoftware.com> writes:
>
> On Thu, 2014-02-06 at 18:56 -0500, Kurt Miller wrote:
> > Various sources indicate that LSI's SAS2008 controllers support TRIM
> > when running their IT firmware (LSI [1] and this list [2]). However, I
> > have not been able to get it working with Dell PERC H200 or H310 cross
> > flashed into LSI IT firmware. Currently I'm testing with Samsung 840 EVO
> > SATA SSDs. I have tried various LSI IT firmware versions (P14, P16, P18)
> > and various Linux distributions (Ubuntu 13.10, Ubuntu 12.04, Ubuntu 14
> > beta, RHEL 7 beta, Fedora 19).
> >
> > Is TRIM working for anyone using LSI SAS2008 controllers?
>
> It turns out yes, TRIM is working for LSI SAS2008 controllers. However,
> the Samsung 840 EVO's are not compatible with it and are also missing
> from the LSI compatibility list for the controller [1]. When I got my
> hands on an SSD that is on the list, TRIM worked as expected.
>
> [1] http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus
> %20Adapters%20Common%20Files/LSI_6Gb_SAS_SATA_HBA_Compatibility_List.pdf
>
> Regards,
> -Kurt
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
I find the Hitachi HUS110 disk storage also does not support fstrim,
actually it supports unmap.
The reason is the lbpme in 'sg_readcap -16' return 0, but the unmap in
'sg_vpd -p 0xb2' return 1.
Maybe the storage is not fully compatible to the SCSI standard.
# sg_readcap -16 /dev/dm-2
Read Capacity results:
Protection: prot_en=0, p_type=0, p_i_exponent=0
Logical block provisioning: lbpme=0, lbprz=1
# sg_vpd --page=0xb2 /dev/dm-2
Logical block provisioning VPD page (SBC):
Unmap command supported (LBPU): 1
Write same (16) with unmap bit supported (LBWS): 1
prev parent reply other threads:[~2015-09-09 1:55 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
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 [this message]
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=loom.20150909T034002-827@post.gmane.org \
--to=changlimin@h3c.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