Date: Thu, 18 Aug 2005 21:57:49 -0700 From: Matthew Jacob <lydianconcepts@gmail.com> To: Eric Anderson <anderson@centtech.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Qlogic (isp driver) gone mad on 6.0 Message-ID: <7579f7fb05081821574d919355@mail.gmail.com> In-Reply-To: <43048653.3010108@centtech.com> References: <430397A2.4010303@centtech.com> <20050817203547.GA28892@uci.agh.edu.pl> <4303A0CC.2060005@centtech.com> <7579f7fb0508171456636c8998@mail.gmail.com> <43048653.3010108@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sounds more like a problem with the target. Make the limit 255- not 256. . >=20 > Well, the system boots faster as it doesn't have to probe 16k devices, > but there's still one problem - it sees the correct 3 luns per device, > but then adds a 'fake' device at lun 256 which is essentially the same > as the first lun. Here's some more info: >=20 > # camcontrol devlist > <PE/PV 1x3 SCSI BP 1.1> at scbus0 target 6 lun 0 (pass0,ses0) > <JetStor snappod1-vol1 R001> at scbus2 target 0 lun 0 (pass1,da0) > <JetStor snappod1-vol2 R001> at scbus2 target 0 lun 1 (pass2,da1) > <JetStor snappod1-vol3 R001> at scbus2 target 0 lun 2 (pass3,da2) > <JetStor snappod1-vol1 R001> at scbus2 target 0 lun 256 (pass4,da3) > <JetStor snappod2-vol1 R001> at scbus2 target 2 lun 0 (pass5,da4) > <JetStor snappod2-vol2 R001> at scbus2 target 2 lun 1 (pass6,da5) > <JetStor snappod2-vol3 R001> at scbus2 target 2 lun 2 (pass7,da6) > <JetStor snappod2-vol1 R001> at scbus2 target 2 lun 256 (pass8,da7) > <JetStor snappod3-vol1 R001> at scbus2 target 3 lun 0 (pass9,da8) > <JetStor snappod3-vol2 R001> at scbus2 target 3 lun 1 (pass10,da9) > <JetStor snappod3-vol3 R001> at scbus2 target 3 lun 2 (pass11,da10) > <JetStor snappod3-vol1 R001> at scbus2 target 3 lun 256 (pass12,da1= 1) > <JetStor snappod1-vol1 R001> at scbus3 target 0 lun 0 (pass13,da12) > <JetStor snappod1-vol2 R001> at scbus3 target 0 lun 1 (pass14,da13) > <JetStor snappod1-vol3 R001> at scbus3 target 0 lun 2 (pass15,da14) > <JetStor snappod1-vol1 R001> at scbus3 target 0 lun 256 (pass16,da1= 5) > <JetStor snappod2-vol1 R001> at scbus3 target 1 lun 0 (pass17,da16) > <JetStor snappod2-vol2 R001> at scbus3 target 1 lun 1 (pass18,da17) > <JetStor snappod2-vol3 R001> at scbus3 target 1 lun 2 (pass19,da18) > <JetStor snappod2-vol1 R001> at scbus3 target 1 lun 256 (pass20,da1= 9) > <JetStor snappod3-vol1 R001> at scbus3 target 3 lun 0 (pass21,da20) > <JetStor snappod3-vol2 R001> at scbus3 target 3 lun 1 (pass22,da21) > <JetStor snappod3-vol3 R001> at scbus3 target 3 lun 2 (pass23,da22) > <JetStor snappod3-vol1 R001> at scbus3 target 3 lun 256 (pass24,da2= 3) >=20 >=20 > You can see that the 'lun 256' marked devices are duplicates. >=20 > Eric >=20 >=20 >=20 >=20 > -- > ------------------------------------------------------------------------ > Eric Anderson Sr. Systems Administrator Centaur Technology > Anything that works is better than anything that doesn't. > ------------------------------------------------------------------------ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7579f7fb05081821574d919355>