> "Mike" == Mike Christie writes:
Mike> Shot, not sure what was tested in that thread now. I tried out
Mike> the newer MS iscsi target, 3.3, and still hit the same issue that
Mike> was reported here.
Mike> What info did you need? Here is vendor/product/version info:
Just sent out a prop
On 12/03/2014 05:00 PM, Martin K. Petersen wrote:
> Mike> j...@deti74.ru's patch would work around the same problem because
> Mike> in sd_read_write_same, sd would see no_write_same is set and not
> Mike> send REPORT SUPPORTED OPERATION.
>
> Yeah.
>
> I still don't have a problem quirking the MS
> "Mike" == Mike Christie writes:
Mike> Are you sure about this? The issue you are talking about and the
Mike> one jazz is is the same issue right?
Oh, I see. I wasn't CC:ed on the first part of this thread so I missed
the fact that it was RSOC that was the problem. I read the mail
yesterday
On 12/2/14, 9:09 PM, Martin K. Petersen wrote:
"Mike" == Michael Christie writes:
Mike,
Mike> This was the issue we worked with Microsoft on wasn’t it? You guys
Mike> figured out it was fixed in their target in a recent release
Mike> right?
The issue we worked recently was wrt. the thin prov
> "Mike" == Michael Christie writes:
Mike,
Mike> This was the issue we worked with Microsoft on wasn’t it? You guys
Mike> figured out it was fixed in their target in a recent release
Mike> right?
The issue we worked recently was wrt. the thin provisioning reporting.
The WRITE SAME problem
Hey Vaughan,
This was the issue we worked with Microsoft on wasn’t it? You guys figured out
it was fixed in their target in a recent release right?
On Dec 1, 2014, at 3:01 AM, vaughan wrote:
> On 12/01/2014 03:25 PM, j...@deti74.ru wrote:
>> I has some sproblem and only one ISCSI target - Micr
On 12/01/2014 03:25 PM, j...@deti74.ru wrote:
> I has some sproblem and only one ISCSI target - Microsoft SWT
> I disable write_same for iscsi by patching kernel (3.17.0)
This method is not good. Below is the answer from Mike when I asked if
we can disable write_same in the template before.
"If y
On 2014年01月11日 04:24, Mike Christie wrote:
On 01/10/2014 02:09 AM, vaughan wrote:
On 01/10/2014 03:41 PM, Mike Christie wrote:
On 1/10/14 12:11 AM, vaughan wrote:
I haven't figure out why it's rejected with "bookmark invalid"(9)
reason, rather than "command not supported". IMO "bookmark inval
On 01/10/2014 02:09 AM, vaughan wrote:
> On 01/10/2014 03:41 PM, Mike Christie wrote:
>> On 1/10/14 12:11 AM, vaughan wrote:
>>> I haven't figure out why it's rejected with "bookmark invalid"(9)
>>> reason, rather than "command not supported". IMO "bookmark invalid" is
>>> used when minor protocol
On 01/10/2014 03:41 PM, Mike Christie wrote:
> On 1/10/14 12:11 AM, vaughan wrote:
>> I haven't figure out why it's rejected with "bookmark invalid"(9)
>> reason, rather than "command not supported". IMO "bookmark invalid" is
>> used when minor protocol conflict such as final flag not set with
>>
On 01/10/2014 03:41 PM, Mike Christie wrote:
> On 1/10/14 12:11 AM, vaughan wrote:
>> I haven't figure out why it's rejected with "bookmark invalid"(9)
>> reason, rather than "command not supported". IMO "bookmark invalid" is
>> used when minor protocol conflict such as final flag not set with
>> n
On 1/10/14 12:11 AM, vaughan wrote:
I haven't figure out why it's rejected with "bookmark invalid"(9)
reason, rather than "command not supported". IMO "bookmark invalid" is
used when minor protocol conflict such as final flag not set with
non-write command. However, I haven't find error of this k
On 01/10/2014 02:38 AM, Mike Christie wrote:
> On 01/09/2014 04:20 AM, vaughan wrote:
>> We are testing linux iscsi boot under UEFI mode with Microsoft iSCSI
>> Software Target. But failed for rejected by target.
>> When do a normal iscsi connection, iscsi connection is keeping rejected
>> and reco
> "Mike" == Mike Christie writes:
>> 2. report_opcode is optional in SPC-3, so it's possible that not all
>> iscsi target support it. But is it correct for microsoft iSCSI target
>> to reject the command rather than return it with normal SCSI
>> response?
Mike> The iscsi spec has the reason
On 01/09/2014 04:20 AM, vaughan wrote:
> We are testing linux iscsi boot under UEFI mode with Microsoft iSCSI
> Software Target. But failed for rejected by target.
> When do a normal iscsi connection, iscsi connection is keeping rejected
> and recover. See below:
>
> Dec 15 20:09:07 ol6u4gx64 kern
We are testing linux iscsi boot under UEFI mode with Microsoft iSCSI
Software Target. But failed for rejected by target.
When do a normal iscsi connection, iscsi connection is keeping rejected
and recover. See below:
Dec 15 20:09:07 ol6u4gx64 kernel: scsi11 : iSCSI Initiator over TCP/IP
Dec 15 20:
16 matches
Mail list logo
