Re: IET chunk + ESXI5

> Well the results are undefined if two disks from different targets with
> different LUNs have the same ScsiSN, so no one can say if explains or
> doesn't explain.
>
> -Ross
>
>
> On Mar 17, 2012, at 7:54 PM, "Yucong Sun (叶雨飞)" <sunyucong@...> wrote:
>
> ahhh, I would try re-configure them right away today, But this doesn't
> really explain the mysteriousness of unknown LUN commands.
>
> And for most time, my current approach actually works fine.
>
> On Sat, Mar 17, 2012 at 4:51 PM, Ross S. W. Walker
> <RWalker@...> wrote:
>> Ahh, problem is ScsiSN must be globally unique between all disks.
>>
>> ESXi thinks they are two paths to the same disk with that config.
>>
>> -Ross
>>
>>
>> On Mar 17, 2012, at 7:48 PM, "Yucong Sun (叶雨飞)" <sunyucong@...>
>> wrote:
>>
>> The problem is I have 2 machines that configured as such:
>>
>> Target iqn.2009-10.com.outofwall:vstore1
>>         Lun 1 Path=/dev/sdb,Type=fileio,ScsiId=vstore1,ScsiSN=1,IOMode=wt
>>
>> Target iqn.2010-09.com.outofwall:vstore2
>>         Lun 0 Path=/dev/sdb,Type=fileio,ScsiId=vstore2,ScsiSN=1,IOMode=wt
>>
>> and if I use the same Lun 0 , ESXi will think they are the same device
>> address
>>
>> t10.94545xxxxxxxxx 673747F627516<LUN number>3000000000
>>
>> I couldn't figure out how to make it not appear to be same address, so
>> I resorted to Lun number difference. what did I do wrong?
>>
>>
>> On Sat, Mar 17, 2012 at 4:40 PM, Ross S. W. Walker
>> <RWalker@...> wrote:
>>> I would definitely make it LUN 0 as there cannot exist a LUN 1 without a
>>> LUN
>>> 0 per the SCSI spec.
>>>
>>> -Ross
>>>
>>>
>>> On Mar 17, 2012, at 7:36 PM, "Yucong Sun (叶雨飞)" <sunyucong@...>
>>> wrote:
>>>
>>> I only have a single target and single LUN, the problem is
>>>
>>> for example , this target only have LUN 1 (no lun 0) , but somehow
>>> esxi is blocked by trying to issue command to LUN0,  The similiar
>>> things happens on another machine which only have LUN 0 configured but
>>>  esxi starts to send traffic to LUN0, what could possibly be the
>>> problem?
>>>
>>> [88410.868981] iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by
>>> sid:283674003964416 (Unknown LUN)
>>> [88412.880949] iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by
>>> sid:283674003964416 (Unknown LUN)
>>> [88414.892930] iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by
>>> sid:283674003964416 (Unknown LUN)
>>>
>>> Cheers.
>>>
>>> On Sat, Mar 17, 2012 at 3:49 AM, Emmanuel Florac <eflorac@...>
>>> wrote:
>>>> Le Fri, 16 Mar 2012 15:56:37 -0700 vous écriviez:
>>>>
>>>>> I'm running trunk .
>>>>>
>>>>
>>>> OK, I've made a new fresh install this week that should be connected to
>>>> an ESXi 5 host, I'll see if anything similar happens. Are you using
>>>> multiple targets, and do you have multiple LUNs on each target?
>>>>
>>>> --
>>>> ------------------------------------------------------------------------
>>>> Emmanuel Florac     |   Direction technique
>>>>                    |   Intellique
>>>>                    |   <eflorac@...>
>>>>                    |   +33 1 78 94 84 02
>>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF email is sponsosred by:
>>> Try Windows Azure free for 90 days Click Here
>>> http://p.sf.net/sfu/sfd2d-msazure
>>> _______________________________________________
>>> Iscsitarget-devel mailing list
>>> Iscsitarget-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
>>>
>>>
>>> ________________________________
>>> This e-mail, and any attachments thereto, is intended only for use by the
>>> addressee(s) named herein and may contain legally privileged and/or
>>> confidential information. If you are not the intended recipient of this
>>> e-mail, you are hereby notified that any dissemination, distribution or
>>> copying of this e-mail, and any attachments thereto, is strictly
>>> prohibited.
>>> If you have received this e-mail in error, please immediately notify the
>>> sender and permanently delete the original and any copy or printout
>>> thereof.
>>
>>
>> ________________________________
>> This e-mail, and any attachments thereto, is intended only for use by the
>> addressee(s) named herein and may contain legally privileged and/or
>> confidential information. If you are not the intended recipient of this
>> e-mail, you are hereby notified that any dissemination, distribution or
>> copying of this e-mail, and any attachments thereto, is strictly
>> prohibited.
>> If you have received this e-mail in error, please immediately notify the
>> sender and permanently delete the original and any copy or printout
>> thereof.
>
>
> ________________________________
> This e-mail, and any attachments thereto, is intended only for use by the
> addressee(s) named herein and may contain legally privileged and/or
> confidential information. If you are not the intended recipient of this
> e-mail, you are hereby notified that any dissemination, distribution or
> copying of this e-mail, and any attachments thereto, is strictly prohibited.
> If you have received this e-mail in error, please immediately notify the
> sender and permanently delete the original and any copy or printout thereof.