Thanks. Yes,I also do it. The parameter only turn off iSCSI pings
test, log show error from kernel,iscsid can only response reopen
action.The debug infomation show:
71686 Sep 26 22:36:47 linux-j2cx kernel: connection1:0: iscsi:
detected conn error (1011)
71687 Sep 26 22:36:48 linux-j2cx iscsid:
PROTECTED] wrote:
Richard wrote:
Thanks. Yes,I also do it. The parameter only turn off iSCSI pings
test, log show error from kernel,iscsid can only response reopen
action.The debug infomation show:
71686 Sep 26 22:36:47 linux-j2cx kernel: connection1:0: iscsi:
detected conn error (1011
: connection1:0 is operational after recovery (1 attempts)
iscsid: thread 0x639f38 schedule: delay 20 state 3
iscsid: noop out timer 0x639f38 start
On Oct 4, 9:56 pm, Richard [EMAIL PROTECTED] wrote:
Thanks,I think need use it.
On Oct 3, 1:42 am, Mike Christie [EMAIL PROTECTED] wrote:
Richard wrote
I'm installing open-iscsi on a dell NX1950 w/ an MD3000. I was able to
start a target daemon as well as an initiator.
My problem is that I can't seem to find my target disks so that I can
partition them and create the file systems. Or maybe I'm not
discovering targets correctly and therefore
?
Thanks
Richard
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To view this discussion on the web visit
https://groups.google.com/d/msg/open-iscsi/-/wWLrESe0kTgJ.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from
side.
--
Richard
signature.asc
Description: This is a digitally signed message part
--
Richard
signature.asc
Description: This is a digitally signed message part
-component isn't
actually exporting this information in any way.
--
Richard
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi
Hi,
Thanks for your help, resolved the issue now. It had been setup to load
the kernel modules and mount the target via the initrd image.
I can't tell you how frustrating that was to diagnose :)
I removed the offending lines, rebuilt the image, then fixed the issue.
Regards
R
On
in my case, it's necessary to restart
libvirt-bin after restarting open-iscsi.
Are many people really using iSCSI via roaming network connectivity?
--
Richard
signature.asc
Description: This is a digitally signed message part
What seems to be happening is that the config files are getting
corrupted in interesting ways such that they have more than 2048 chars
in a line without an NL.
Eg:
---
/var/lib/iscsi/nodes/iqn.2010-06.com.nutanix:volumegroup-
and actually
causes things to take longer and is a problem when you are trying to
start hundreds of iSCSI sessions.
There is another patch for the LLD to use a WQ_HIGHPRI queue to
achieve the original intent.
--
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)
--
You received this message because you
No functional change.
>
> This one smells like an abuser. Why the hell should read/write path
> touch memory reserves at all!
Could be. Let's ask Adrian, AFAIK he wrote that code.
Adrian, can you please clarify why nandsim needs to play with PF_MEMALLOC?
Thanks,
//richard
--
You received this mess
13 matches
Mail list logo