Date: Tue, 18 May 2010 17:59:05 -0600 From: Scott Long <scottl@samsco.org> To: Matthew Jacob <mj@feral.com> Cc: freebsd-scsi@freebsd.org Subject: Re: going rogue: incorporating REPORT_LUNS into the SCSI probe sequence Message-ID: <76ECB3BB-6862-4DCE-8CC9-35ED1BC70BD2@samsco.org> In-Reply-To: <4BF19453.8090801@feral.com> References: <4BF19453.8090801@feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 17, 2010, at 1:09 PM, Matthew Jacob wrote: > This one is a bit rougher than the others, but I'd like to encourage some discussion about this. > > The problems presented by not using REPORT LUNS have been getting uglier and uglier. Any kind of sparse lun arrangement for large JBODs or RAID units just makes life very painful. > > These changes manage REPORT LUNS for devices > SPC2, and even manage changes in the list. These changes do *not* address the edge case of having no attached LUN 0 (which has been known to happen- it's not illegal). Under what circumstance is it not illegal? I thought that in SPI it was always illegal. Granted, FC and other protocols might be different, hence my curiosity. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76ECB3BB-6862-4DCE-8CC9-35ED1BC70BD2>