EddyQ wrote:
Does open-iscsi support long CDBs?
You still need one more patch:
http://www.spinics.net/lists/linux-scsi/msg26927.html
Mike please push it threw your tree, James has gone mute
Just out of curiosity, what are you using long CDBs for?
Cheers
Boaz
Just trying to get my code fully tested.
Eddy
-Original Message-
From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Boaz Harrosh
Sent: Wednesday, June 04, 2008 4:15 AM
To: open-iscsi@googlegroups.com; Mike Christie; EddyQ
Subject: Re: Long CDBs
EddyQ wrote:
Does
So I just tried issuing a logout with iscsiadm. After this I was able
to umount and reboot no problem. Even though the iSCSI device can't
respond does this command set something in the Kernel when it doesn't
receive an ACK?
-JD
On Jun 2, 3:16 am, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
Wanted to update on this issues again ...
It just means that userspace tried to set a feature the kernel did not
support. It is not serious.
If there was nothing before that first line about the kernel reporting a
connection error, then the target could have initiated this. Do you see
Hello all,
I have been wondering a given scenario, where a server boots linux
over iscsiRoot; how would iscsi initiator handle, if for instance,
access to the iscsiRoot device is interrupted for a second or two. A
situation where this could possibly occur would be if one would add a
new target
a s p a s i a wrote:
Hello all,
I have been wondering a given scenario, where a server boots linux
over iscsiRoot; how would iscsi initiator handle, if for instance,
access to the iscsiRoot device is interrupted for a second or two. A
situation where this could possibly occur would be if
a s p a s i a wrote:
Wanted to update on this issues again ...
It just means that userspace tried to set a feature the kernel did not
support. It is not serious.
If there was nothing before that first line about the kernel reporting a
connection error, then the target could have initiated
Mike Christie wrote:
a s p a s i a wrote:
Wanted to update on this issues again ...
It just means that userspace tried to set a feature the kernel did not
support. It is not serious.
If there was nothing before that first line about the kernel reporting a
connection error, then the target
An Oneironaut wrote:
So I just tried issuing a logout with iscsiadm. After this I was able
to umount and reboot no problem. Even though the iSCSI device can't
respond does this command set something in the Kernel when it doesn't
receive an ACK?
If the connection is not up, and you run
Thanks for the response!! I will thoroughly review the readme and
feedback any observations.
One question - how do I check whether the config parameter change has
been set correctly? Do I just look at the config file in the
/etc/iscsi/nodes/ etc/default? does not seem to show in
Oh yeah, are you doing anything on the target? Rebooting it? Changing
the config? Adding or removing targets or portals?
in the target when the /etc/ietd.conf file is updated with a new
iscsi root, a brief service iscsi-target restart occurs we're
thinking of just keeping a static list
11 matches
Mail list logo