Date: Sat, 14 Sep 2002 10:57:36 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Matthew Emmerton <matt@gsicomp.on.ca> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Strange output from camcontrol Message-ID: <20020914095736.GB46500@happy-idiot-talk.infracaninophi> In-Reply-To: <004101c25b99$0a6302a0$1200a8c0@gsicomp.on.ca> References: <004101c25b99$0a6302a0$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 13, 2002 at 10:47:17PM -0400, Matthew Emmerton wrote:
> I'm runing 4.4-REL and I'm getting strange output from camcontrol:
>
> gabby# camcontrol devlist -v
> scbus0 on ahc0 bus 0:
> <SEAGATE ST32430N 0510> at scbus0 target 0 lun 0 (pass0,da0)
> <FUJITSU M2694ES-512 8134> at scbus0 target 4 lun 0 (pass1,da1)
> <OEM DCRS04Z 0101> at scbus0 target 6 lun 0 (pass2,da2)
> < > at scbus0 target -1 lun -1 ()
> scbus-1 on xpt0 bus 0:
> < > at scbus-1 target -1 lun -1 (xpt0)
>
> I'm confused about:
> - why ahc0 lists target -1 lun -1
That's normal. The '< >' entries are just a marker for "end of list"
--- either the inner lists of devices on each scbus, or the 'scbus-1'
marks the end of the outer list of scbus-es.
> - why I'm getting scbus-1 listed on xpt0 (a device that isn't even listed in
> LINT)
That's the CAM transport layer interface. See xpt(4). It doesn't
require any kernel configuration support (so no LINT entries) --- it
will be there automatically if there's any CAM subsystem operational.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020914095736.GB46500>