On Dec 28, 2011, at 9:33 AM, Mike Christie wrote:
> What is that problem? Don't get anything from the target, crash, etc?
Noting. iscsiadm just hangs there...
But this is a different problem from before, one that I don't care
if you fix or not :).
I start ietd on the physical host and the iscsid inside the chroot
(since that previously worked best and that's where I use my targets).
If I now try to do a discovery from the physical host, that process
hangs.
BUT, if I instead start iscsid on the physical host (i.e. outside
the chroot), then it works everywhere, just as expected.
PS. The _only_ thing I got in either ietd or iscsid logs (running with
'-f -d9' and '-f -d8' respectivly) when running as I used to was
ONE line (in the iscsid output/log):
iscsid: poll result 1
But since it works, I consider this problem closed now when I run
as I'm supposed to :). Thanx a mill for all the help, much appreciated!
--
Try not. Do. Or do not. There is no try!
- Yoda
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
