From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: mdw@linuxbox.com
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: Re: Intel 520/530 SSD for ceph
Date: Thu, 21 Nov 2013 09:36:07 +0100 [thread overview]
Message-ID: <528DC5F7.6040104@profihost.ag> (raw)
In-Reply-To: <20131121002936.GA15558@soma.private.linuxbox.com>
Hi,
Am 21.11.2013 01:29, schrieb mdw@linuxbox.com:
> On Tue, Nov 19, 2013 at 09:02:41AM +0100, Stefan Priebe wrote:
> ...
>>> You might be able to vary this behavior by experimenting with sdparm,
>>> smartctl or other tools, or possibly with different microcode in the drive.
>> Which values or which settings do you think of?
> ...
>
> Off-hand, I don't know. Probably the first thing would be
> to compare the configuration of your 520 & 530; anything that's
> different is certainly worth investigating.
>
> This should display all pages,
> sdparm --all --long /dev/sdX
> the 520 only appears to have 3 pages, which can be fetched directly w/
> sdparm --page=ca --long /dev/sdX
> sdparm --page=co --long /dev/sdX
> sdparm --page=rw --long /dev/sdX
>
> The sample machine I'm looking has an intel 520, and on ours,
> most options show as 0 except for
> AWRE 1 [cha: n, def: 1] Automatic write reallocation enabled
> WCE 1 [cha: y, def: 1] Write cache enable
> DRA 1 [cha: n, def: 1] Disable read ahead
> GLTSD 1 [cha: n, def: 1] Global logging target save disable
> BTP -1 [cha: n, def: -1] Busy timeout period (100us)
> ESTCT 30 [cha: n, def: 30] Extended self test completion time (sec)
> Perhaps that's an interesting data point to compare with yours.
>
> Figuring out if you have up-to-date intel firmware appears to require
> burning and running an iso image from
> https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18455
>
> The results of sdparm --page=<whatever> --long /dev/sdc
> show the intel firmware, but this labels it better:
> smartctl -i /dev/sdc
> Our 520 has firmware "400i" loaded.
Firmware is up2date and all values are the same. I expect that the 520
firmware just ignores CMD_FLUSH commands and the 530 does not.
Greets,
Stefan
prev parent reply other threads:[~2013-11-21 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 13:38 Intel 520/530 SSD for ceph Stefan Priebe - Profihost AG
[not found] ` <528A1862.7010601-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-18 22:51 ` mdw-Jp3n8lUXroRWk0Htik3J/w
[not found] ` <20131118225146.GA1043-Hsy7OnahZ0C224KT6AusD78MeWzc+u9DAL8bYrjMMd8@public.gmane.org>
2013-11-19 8:02 ` Stefan Priebe
[not found] ` <528B1B21.1060203-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-21 0:29 ` mdw-Jp3n8lUXroRWk0Htik3J/w
2013-11-21 8:36 ` Stefan Priebe - Profihost AG [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=528DC5F7.6040104@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.com \
--cc=mdw@linuxbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.