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
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 kernel:
On Thursday, January 9, 2014 10:38:15 AM UTC-8, Mike Christie wrote:
...
There are some questions:
1. Why stgt target don't has this issue? Does it support report_opcode
because it has a embeded controller lun0? Or it just returns INVALID in
response?
Don't know. Will let someone
I notice that Ubuntu has an installation option to install directly to an
iScsi target .
I assume this means that the intelligence to boot a kernel with the proper
bootags passed in using the default initrd.gz can be px(bootp) e booted
into a iscsi diskless environment?
I recall trying iscsi
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 recover. See
Mike == Mike Christie micha...@cs.wisc.edu 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
Dear All,
Is there a way to configure logging of iSCSI to some other file than
/var/log/messages.
I think by default iSCSI logs gets created in syslog(/var/log/messages), i
want to have iSCSI logs in some different file.
--
You received this message because you are subscribed to the Google
Did this not get merged? I'm seeing a connection refused in a strace
output of iscsiadm -m session -P 3
20599 write(1, Target: iqn.2010-01.com.myhostname..., 53) = 53
20599 write(1, \tCurrent Portal: 172.16.0.115:32..., 37) = 37
20599 write(1, \tPersistent Portal: 172.16.0.115..., 40) = 40
Hello,
when trying to connect open-iscsi in initiator mode to solaris target I
have encountered situation when accessing of iscsi device causes hang on
kernel call.
iscsi successfully logs on to targets, devices /dev/sdc and /dev/sdd (one
for IPv4 and another for IPv6) are created, by trying
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 kind
On 1/9/14 9:17 PM, Fred Smit wrote:
I notice that Ubuntu has an installation option to install directly to an
iScsi target .
I assume this means that the intelligence to boot a kernel with the proper
bootags passed in using the default initrd.gz can be px(bootp) e booted
into a iscsi diskless
A version of the patch has been merged in the upstream tree. Not sure if
it has made it into all the distos.
On 1/3/14 11:45 AM, c.hendrickso...@gmail.com wrote:
Did this not get merged? I'm seeing a connection refused in a strace
output of iscsiadm -m session -P 3
20599 write(1, Target:
On 1/4/14 8:08 AM, fidoman...@gmail.com wrote:
Hello,
when trying to connect open-iscsi in initiator mode to solaris target I
have encountered situation when accessing of iscsi device causes hang on
kernel call.
iscsi successfully logs on to targets, devices /dev/sdc and /dev/sdd (one
for IPv4
13 matches
Mail list logo
