Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Sep 2012 14:18:18 +0530
From:      "Desai, Kashyap" <Kashyap.Desai@lsi.com>
To:        Jason Keltz <jas@cse.yorku.ca>, "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>
Subject:   RE: mps target difference between FreeBSD 9 and 9.1 RC
Message-ID:  <B2FD678A64EAAD45B089B123FDFC3ED75E63221ED8@inbmail01.lsi.com>
In-Reply-To: <505A2614.2000709@cse.yorku.ca>
References:  <505A2614.2000709@cse.yorku.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Jason:

FreeBSD9.0 is very old driver where we don't have "mps_mapping.c". With mps=
_mapping.c we are supporting different Target ID mapping which is main reas=
on why you are seeing two different target ID behaviors in this case.

We have major two mapping method.
1. enclosure slot mapping and
2. Device mapping.

Depends upon what you have configured in FW Driver will behave accordingly.

I would suggest to flash your Card completely and start from fresh with onl=
y FreeBSD-9.1. do not compare FreeBSD-9.0


` Kashyap

> -----Original Message-----
> From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd-
> scsi@freebsd.org] On Behalf Of Jason Keltz
> Sent: Thursday, September 20, 2012 1:38 AM
> To: freebsd-scsi@freebsd.org
> Subject: mps target difference between FreeBSD 9 and 9.1 RC
>=20
> I have a Dell R720 and a 24 x 2.5" Dell MD1220 JBOD.   I have added dual
> LSI 9205-8e, each connected to the same MD1220 array.  Under FreeBSD
> 9.0, if I do a "camcontrol devlist" (with every other disk removed), I
> see:
>=20
> <WD WD9001BKHG D1S2>               at scbus0 target 0 lun 0 (pass0,da0)
> <WD WD9001BKHG D1S2>               at scbus0 target 2 lun 0 (pass1,da1)
> <WD WD9001BKHG D1S2>               at scbus0 target 4 lun 0 (pass2,da2)
> <WD WD9001BKHG D1S2>               at scbus0 target 6 lun 0 (pass3,da3)
> <WD WD9001BKHG D1S2>               at scbus0 target 8 lun 0 (pass4,da4)
> <WD WD9001BKHG D1S2>               at scbus0 target 10 lun 0 (pass5,da5)
> <DELL MD1220 1.01>                 at scbus0 target 36 lun 0
> (pass6,ses0)
> <WD WD9001BKHG D1S2>               at scbus1 target 12 lun 0 (pass7,da6)
> <WD WD9001BKHG D1S2>               at scbus1 target 14 lun 0 (pass8,da7)
> <WD WD9001BKHG D1S2>               at scbus1 target 16 lun 0 (pass9,da8)
> <WD WD9001BKHG D1S2>               at scbus1 target 18 lun 0
> (pass10,da9)
> <WD WD9001BKHG D1S2>               at scbus1 target 21 lun 0
> (pass11,da10)
> <WD WD9001BKHG D1S2>               at scbus1 target 22 lun 0
> (pass12,da11)
> <DELL MD1220 1.01>                 at scbus1 target 36 lun 0
> (pass13,ses1)
> <TEAC DVD-ROM DV-28SW R.2A>        at scbus6 target 0 lun 0 (pass14,cd0)
>=20
> ... which is what I would expect.  If I do the same thing with any
> pre-release/RC version of 9.1, I see:
>=20
> <WD WD9001BKHG D1S2>               at scbus0 target 34 lun 0 (pass0,da0)
> <WD WD9001BKHG D1S2>               at scbus0 target 36 lun 0 (pass1,da1)
> <WD WD9001BKHG D1S2>               at scbus0 target 38 lun 0 (pass2,da2)
> <WD WD9001BKHG D1S2>               at scbus0 target 39 lun 0 (pass3,da3)
> <WD WD9001BKHG D1S2>               at scbus0 target 41 lun 0 (pass4,da4)
> <WD WD9001BKHG D1S2>               at scbus0 target 43 lun 0 (pass5,da5)
> <DELL MD1220 1.01>                 at scbus0 target 45 lun 0
> (ses0,pass6)
> <WD WD9001BKHG D1S2>               at scbus1 target 21 lun 0 (pass7,da6)
> <WD WD9001BKHG D1S2>               at scbus1 target 23 lun 0 (pass8,da7)
> <WD WD9001BKHG D1S2>               at scbus1 target 24 lun 0 (pass9,da8)
> <WD WD9001BKHG D1S2>               at scbus1 target 26 lun 0
> (pass10,da9)
> <WD WD9001BKHG D1S2>               at scbus1 target 29 lun 0
> (pass11,da10)
> <WD WD9001BKHG D1S2>               at scbus1 target 31 lun 0
> (pass12,da11)
> <DELL MD1220 1.01>                 at scbus1 target 32 lun 0
> (ses1,pass13)
> <TEAC DVD-ROM DV-28SW R.2A>        at scbus6 target 0 lun 0 (pass14,cd0)
>=20
> In particular, note how the targets are starting at 34.  I wonder if
> someone might explain why?
>=20
> I was considering using /boot/device.hints to hard-code the daX mapping
> to avoid the use of "labels" for my volumes,  but I wouldn't expect the
> targets to change between the two releases.
>=20
> Thanks for any information that you can provide..
>=20
> Jason.
>=20
> _______________________________________________
> freebsd-scsi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"



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