Matthew Schumacher wrote:
Mike Christie wrote:
I found another issue: When using open-iscsi-2.0_869.2 on 2.6.24.5
everything works as described above. You can restart iscsid and all is
well. If I switch to open-iscsi-2.0_871_2
Where did you get 871.2? There is only a 871 on
Matthew Schumacher wrote:
Mike Christie wrote:
When you kill iscsid, are there sessions running? If there are then when
you run iscsid below you should not have to rerun your discovery command
and run the login command. iscsid basically looks at
/sys/class/iscsi_session and will logout
Hello Group,
I'm working out the config to boot a host from an iscsi target and have
everything pretty much working, but once the host is up, I can't connect
to any other iscsi targets.
My initrd script calls the following:
Matthew Schumacher wrote:
Hello Group,
I'm working out the config to boot a host from an iscsi target and have
everything pretty much working, but once the host is up, I can't connect
to any other iscsi targets.
My initrd script calls the following:
On 07/28/2009 06:59 PM, Matthew Schumacher wrote:
Mike Christie wrote:
This is what we do in Red Hat. It is a little tricky, because when
iscsid restarts it relogins into the target to make sure its state is
all in sync with the kernel and session. So the network has to be up
first, then
