On Tue, 2012-02-07 at 15:39 +0800, Jim Barber wrote: > On 7/02/2012 2:54 AM, Roland Dreier wrote: > > > > Unfortunately there isn't really a good branch for qla2xx target stuff > > at the moment. qla_tgt-3.3 is probably the best as far as the specific > > qla2xxx driver, but as you noticed it is missing some core fixes. And > > the qla2xxx driver is still buggy -- in fact I have some fixes I need to > > send out soon. > > > > - R. > > Okay thanks. Hello Jim, Just a brief follow-up to your recent questions. For tracking the mainline WIP qla2xxx target code in my tree, you want to be using lio-core.git/master currently @ linus v3.2.0. The qla_tgt-3.3 branch has been merged into master earlier this year so I'm no longer putting updates into the old working branch, and will be removed soon. > The only reason I ask is that I've rebooted the Linux SAN a few times to > get past an error that occurs once or twice a week. > I'm provisioning disk to ESXi 5.0 servers and have some test VMs on it. > When the error occurs the logs look like the following: > As for the log below, it appears an outstanding CTIO descriptor is being returned from HW with CTIO_ABORTED (0x2) status.. >From there the FC sessions are being reset locally and we run into problems with QLA_TGT_NEXUS_LOSS_SESS not being supported yet. These are both something that does need to be addressed, and that I will be resolving soon. > Feb 3 16:54:44 san kernel: [356059.826049] Uknown TMR function: 0x0d. > Feb 3 16:54:44 san kernel: [356059.832404] qla_target(0): CTIO with status 0x2 received, state 3, se_cmd ffff880037212758, > (LIP_RESET=e, ABORTED=2, TARGET_RESET=17, TIMEOUT=b, INVALID_RX_ID=8) > Feb 3 16:54:44 san kernel: [356059.832497] qla2xxx 0000:0b:00.0: qla2x00_error_entry: error entry, type 0x12 status 0x8 > Feb 3 16:54:46 san kernel: [356062.475601] qla2xxx 0000:0b:00.0: qla2x00_error_entry: error entry, type 0x12 status 0x8 > Feb 3 16:55:39 san kernel: [356115.018438] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:55:39 san kernel: [356115.018495] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:55:39 san kernel: [356115.020388] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:55:39 san kernel: [356115.020448] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:55:39 san kernel: [356115.020596] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:55:39 san kernel: [356115.020651] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:56:21 san kernel: [356157.240981] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:56:21 san kernel: [356157.241038] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:56:21 san kernel: [356157.243038] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:56:21 san kernel: [356157.243095] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:56:21 san kernel: [356157.243247] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:56:21 san kernel: [356157.243303] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:57:22 san kernel: [356217.700541] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:57:22 san kernel: [356217.700597] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:57:22 san kernel: [356217.702623] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:57:22 san kernel: [356217.702679] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:57:22 san kernel: [356217.702829] scsi(5): resetting (session ffff880125e55d40 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 3 16:57:22 san kernel: [356217.702884] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 3 16:57:37 san kernel: [356233.029437] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000001 > Feb 3 16:57:37 san kernel: [356233.029469] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000001 > Feb 3 16:57:37 san kernel: [356233.029629] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000002 > Feb 3 16:57:37 san kernel: [356233.029672] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000002 > Feb 3 16:57:37 san kernel: [356233.029834] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000003 > Feb 3 16:57:37 san kernel: [356233.030016] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000003 > > The 'Detected NON_EXISTENT_LUN Access' error then persist until I reboot. > I'm not sure if there is something I can do to avoid this error or not. > I was hoping the fixes in the master branch may have been the solution :) > You should still definitely *not* be seeing NON_EXISTENT_LUN errors after a session reset, regardless of the unsupported bits mentioned above. What does your running qla2xxx configuration look like..? Also, what lio-core.git HEAD is this with again..? > Here's another more recent one as well for good measure: > > Feb 6 16:00:39 san kernel: [189694.118344] Uknown TMR function: 0x0d. > Feb 6 16:00:39 san kernel: [189694.120723] qla_target(0): CTIO with status 0x2 received, state 3, se_cmd ffff88008621a3e0, > (LIP_RESET=e, ABORTED=2, TARGET_RESET=17, TIMEOUT=b, INVALID_RX_ID=8) > Feb 6 16:00:39 san kernel: [189694.120773] qla2xxx 0000:0b:00.0: qla2x00_error_entry: error entry, type 0x12 status 0x8 > Feb 6 16:00:42 san kernel: [189697.107084] qla2xxx 0000:0b:00.0: qla2x00_error_entry: error entry, type 0x12 status 0x8 > Feb 6 16:01:34 san kernel: [189749.150380] scsi(5): resetting (session ffff88011a632ec0 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 6 16:01:34 san kernel: [189749.150409] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 6 16:01:34 san kernel: [189749.152436] scsi(5): resetting (session ffff88011a632ec0 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 6 16:01:34 san kernel: [189749.152467] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 6 16:01:34 san kernel: [189749.152614] scsi(5): resetting (session ffff88011a632ec0 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 6 16:01:34 san kernel: [189749.152669] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 6 16:02:16 san kernel: [189791.271422] scsi(5): resetting (session ffff88011a632ec0 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 6 16:02:16 san kernel: [189791.271480] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 6 16:02:16 san kernel: [189791.273482] scsi(5): resetting (session ffff88011a632ec0 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 6 16:02:16 san kernel: [189791.273542] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 6 16:02:16 san kernel: [189791.273703] scsi(5): resetting (session ffff88011a632ec0 from port 21:00:00:1b:32:83:f3:c6, mcmd > fffd, loop_id 130) > Feb 6 16:02:16 san kernel: [189791.273758] qla_target(0): Unknown task mgmt fn 0xfffd > Feb 6 16:02:45 san kernel: [189820.350693] TARGET_CORE[qla2xxx]: Detected NON_EXISTENT_LUN Access for 0x00000001 > > Thanks, --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
