Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	list linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [sucess] upgrading LSI SAS9211-8i fw IR->IT
Date: Fri, 3 Nov 2017 08:54:20 +0800	[thread overview]
Message-ID: <31706ffc-3a81-b844-261e-a84dd8c01deb@fnarfbargle.com> (raw)
In-Reply-To: <34e5cc74-2cb2-5059-0e11-8f26a8bee223@eyal.emu.id.au>

On 02/11/17 18:51, Eyal Lebedinsky wrote:

> What I noted so far:
> - the heat sink feels very hot even after short usage.

Yeah, they do get warm. Best to make sure you have a bit of airflow over 
them. It doesn't take much air movement to keep temps in check.

> - the disks were now in a different order, pretty much reverse order.
>    I am not sure the order will remain fixed (by port number?) or 
> variable (as the disks spin up).

The driver scans them in port/slot order, and apparently in order of 
increasing pci address in the case of multiple cards. In my case where I 
have staggered spinup enabled it spins them up in groups and then waits 
for them in order, so things don't tend to move around unless you shift 
hardware about or a drive fails.

Make sure you do a periodic lsdrv just for records sake, but as yet I've 
not needed it. I keep a spreadsheet which lists which drive S/N is in 
which physical slot so when something happens I can just look up which 
drive needs to be popped without risk of pulling the wrong disk.

I swapped out a set of highpoint controllers for these LSI units back in 
2011 and it was the best thing I ever did for storage speed and reliability.


  reply	other threads:[~2017-11-03  0:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 11:47 upgrading LSI SAS9211-8i fw IR->IT Eyal Lebedinsky
2017-10-24 12:14 ` Roman Mamedov
2017-10-24 13:04   ` Eyal Lebedinsky
2017-10-24 17:59     ` Roman Mamedov
2017-10-26  3:31 ` [sucess?] " Eyal Lebedinsky
2017-10-27 23:09   ` Eyal Lebedinsky
2017-10-29 15:02     ` Brad Campbell
2017-11-02 10:51   ` [sucess] " Eyal Lebedinsky
2017-11-03  0:54     ` Brad Campbell [this message]
2017-11-03  2:31       ` Eyal Lebedinsky
2017-11-03  3:03         ` Brad Campbell
2017-11-03  3:39           ` Eyal Lebedinsky
2017-11-06 20:15         ` Wolfgang Denk
2017-11-06 21:38           ` Eyal Lebedinsky
2017-11-06 21:48             ` Phil Turmel
2017-11-06 21:59               ` Eyal Lebedinsky

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=31706ffc-3a81-b844-261e-a84dd8c01deb@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-raid@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