From: Roman Mamedov <rm@romanrm.net>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: list linux-raid <linux-raid@vger.kernel.org>
Subject: Re: upgrading LSI SAS9211-8i fw IR->IT
Date: Tue, 24 Oct 2017 22:59:26 +0500 [thread overview]
Message-ID: <20171024225926.48873932@natsu> (raw)
In-Reply-To: <fd16035d-adaa-ddc5-1726-7b3873871853@eyal.emu.id.au>
On Wed, 25 Oct 2017 00:04:37 +1100
Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
> I want to avoid the risk of the IR fw writing any metadata to the disks which already
> hold a software RAID.
>
> Is it not the case that the IR fw may mess with the disks (I read a comment suggesting it might)?
I believe when HW RAID controllers do that, they set up HPA to reserve a small
area at the end, and write the metadata there. But just checked, there is no
HPA on any of the 3 disks that I have connected.
$ sudo hdparm -N /dev/sdi
/dev/sdi:
max sectors = 3907029168/3907029168, HPA is disabled
$ sudo hdparm -N /dev/sdh
/dev/sdh:
max sectors = 3907029168/3907029168, HPA is disabled
$ sudo hdparm -N /dev/sdg
/dev/sdg:
max sectors = 3907029168/3907029168, HPA is disabled
You can test by connecting some disk with data you don't care about, and
checking if its contents get modified (especially at the end), or if it gets
HPA enabled.
--
With respect,
Roman
next prev parent reply other threads:[~2017-10-24 17:59 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 [this message]
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
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=20171024225926.48873932@natsu \
--to=rm@romanrm.net \
--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