Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 09 May 2020 23:19:10 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 246279] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
Message-ID:  <bug-246279-227-QNkmSpuir9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-246279-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-246279-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246279

--- Comment #8 from Peter Eriksson <pen@lysator.liu.se> ---
Created attachment 214328
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D214328&action=
=3Dedit
Patch to fix support for more than 48 drives in HBA mode

The attached patch will fix a couple of bugs in the current ciss driver code
where it incorrectly enumerates physical drives if the controller is in JBOD
mode.

There are two bugs/problems:

1. If you attach more physical drives to a controller than how many logical
volumes the controller supports (yes, really - totally wrong logic here) the
additional drives will not be available because the driver sets the max_tar=
get
limit to the number of logical volumes, but the enumeration of hardware dri=
ves
starts at 16. So for a controller that support say 64 logical volumes, only=
 the
first (64-16) drives will
be detected.

2. The code also sets the initiator_id to same max logical volume number so=
 any
physical drive that happens to have the same target number will silently be
skipped...

The patch also enables a little more verbosity.

This patch has been tested with HP H241 controllers in JBOD mode with 70 dr=
ives
connected to a HP D6020 external SAS enclosure on FreeBSD 12.1-RELEASE-p3.=
=20

This patch has not been tested with controllers in "RAID" mode but the patch
should be compatible...

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246279-227-QNkmSpuir9>