re details, but I'm rather new to iscsi and
not really sure what
information is relevant.
- Thomas
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from
E. Wai
> Yes, I believe kernel 232 already has some of those fixes which resolved
> our experience with the LEFTHAND target.
OK, I will try the 232 kernel and see how it works.
M. Christie
> Do these errors start a little after the login? If so then it could be
> due to the target or the initiat
Running with the 232 test kernel, the errors persist.
/var/log/messages
Nov 20 12:39:52 pxfs02 kernel: connection1:0: detected conn error
(1011)
Nov 20 12:39:52 pxfs02 iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Nov 20 12:39:54 pxfs02 kernel: bnx2i [04:00.00]: ISCSI_INIT p
On Nov 22, 9:36 am, Mike Christie wrote:
> On 11/20/2010 02:53 PM, Thomas wrote:
>
> > Running with the 232 test kernel, the errors persist.
>
> > /var/log/messages
> > Nov 20 12:39:52 pxfs02 kernel: connection1:0: detected conn error
> > (1011)
>
I should point out that with the 232 kernel, these messages no longer
get logged and hopefully the events do no longer occur.
kernel: connection1:0: received itt 0 expected session age (c)
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post
On Nov 24, 2:40 pm, Mike Christie wrote:
> For the abort/remote close case, I would look in the target logs to
> check if the target dropped the session.
My apologies if this just fills the forum with useless logs, but here
are logs from two
services (dbd_store and dbd_manager) on the LeftHand
Hello,
Could you please send the mib,snmpwalk output of EqualLogic.If it supports
SMI-s could you post the mof files for the same.Or is there any other
way(CLI Interface)to monitor equallogic...?
On Tue, Jul 28, 2009 at 11:42 PM, Mike Christie wrote:
>
> Ulrich Windl wrote:
> > On 28 Jul 2009 at
nother would connect to
192.168.0.3.
Is there anything we can do about this? We would like to share the
load on these two nodes in stead of doing everything on one node.
Don't hesitate to ask if you need more details on the setup, I'm just
not that familiar with open-iscsi yet.
Kind reg
On Oct 19, 1:55 am, Mike Christie wrote:
> On 10/18/2010 04:15 AM, thomas wouters wrote:
>
>
>
>
>
> > Hi,
>
> > We have an HP Lefthand cluster with currently two storage nodes.
> > This weekend we've done a maintenance on one of the nodes and noticed
On Oct 22, 5:47 pm, thomas wouters wrote:
> On Oct 19, 1:55 am, Mike Christie wrote:
>
>
>
>
>
> > On 10/18/2010 04:15 AM, thomas wouters wrote:
>
> > > Hi,
>
> > > We have an HP Lefthand cluster with currently two storage nodes.
> > >
ipc.c solves my problem.
Is there a chance to fix this issue just by checking if the user has
sufficient rights, e.g. has uid=0, or is there any special reason for
demanding a user named root?
Thanks a lot
Thomas
--
You received this message because you are subscribed to the Google Groups
"
he multiple login issue.
I guess it would be enough just to check if the user that calls
iscsiadm has uid=0 and not the name "root", because if uid=0 the user
is definitively a root user with sufficient privileges.
Kind regards
Thomas
--
You received this message because you are subs
to replace the check for username "root" to a
check for uid 0.
Kind regards
Thomas
On 11 Nov., 08:05, "Ulrich Windl"
wrote:
> Hi!
>
> I wonder whether "sudo" could solve your problem.
>
> Ulrich
>
> >>> Thomas Weichert schrieb am 10.
care
about any permission or security policies. So, thanks for explaining
the technical insights about usernames and ids - however, this does
not change the fact, that there is a bug in open-iscsi.
Kind regards
Thomas
--
You received this message because you are subscribed to the Google Groups
S for production classes that I do not give myself, but will run the
Nab's tree as soon as I give a VMware class myself in order to reproduce
the issue and than track it down.
Cheers,
Thomas
--
You received this message because you are subscribed to the Google Groups
"open-iscsi&q
Hallo Nab,
> Mike's talking about the WIP scsi-mq -> blk-mq initiator stack here,
> and not specifically about anything related to target code.
I see. Thanks. I'll keep you posted.
Cheers,
Thomas
--
You received this message because you are subscribed to the Google
Hi folks,
I spent some time browsing through this forum but I was unable to find an
explanation for this comment referring to the disabled bind_src_by_address()
function in io.c:
*This is not supported for now, because it is not exactly what we want.*
*It also turns out that targets will send p
stie wrote:
...
>
> Thomas, let me know if your question was for functionality you needed or
> just looking through the code and were curious.
>
>
It's functionality that I really want. In fact, I'm here in this forum
because strace on iscsid showed it was never calling bind(
Currently, open-iscsi ignores iface.ipaddress whether or not
iface.net_ifacename is configured. This can be problematic if/when a
network interface is configured with multiple IP addresses and a target
only allows connections from one of them. This patch adds support for
iface.ipaddress, callin
Tom.III
On Tuesday, March 31, 2015 at 10:44:46 AM UTC-7, Thomas Dwyer III wrote:
>
> Currently, open-iscsi ignores iface.ipaddress whether or not
> iface.net_ifacename is configured. This can be problematic if/when a
> network interface is configured with multiple IP addresses and a
Oops...I didn't notice before posting that the "Post Reply" button in
google groups quoted the original message in this thread rather than the
most recent message. :-(
Tom.III
On Monday, April 6, 2015 at 10:23:04 AM UTC-7, Thomas Dwyer III wrote:
>
> I wasn't able
I had a similar issue (assuming target and initiator are on the same host),
the following got it to work for me.
# 1 make sure the services for iscsi initiator, daemon, network, and target
are started in the following order
S09iscsi-target
S10network
S11iscsi
S12iscsid
# 2 /etc/fstab looks like
22 matches
Mail list logo
