On Wed, Feb 24, 2010 at 10:54:57PM +0200, Pasi Kärkkäinen wrote:
> On Wed, Feb 24, 2010 at 12:31:30PM -0800, guymatz wrote:
> > Yeah, again, thanks, but that doesn't help me check to see if the LUN
> > is already mounted on another server, and which one.
> >
>
> You can only see that from the iSC
Mike Christie wrote:
> I am fine with either. The netdev name (ethX) also has the same problems
> where udev can change it. It is there for aliases or vlans where we
> cannot use hwaddress since multiple netdevs have the same MAC.
yes, correct both netdevice name and hwaddress suffer from what you
Mike Christie wrote:
> The nop watch dog is more of generic catch all problems. I think I was
> saying offlist that iscsi_tcp is not able to detect many transport
> problems quickly. For example if you just pulled a cable somewhere in
> the network, iscsi_tcp may not get some event telling us this.
Hello Mike,
On Friday 26 Feb 2010 00:24:29 Mike Christie wrote:
> On 02/25/2010 01:55 AM, Ritesh Raj Sarraf wrote:
> > From: Ritesh Raj Sarraf
>
> Thanks for the patches. Could you tell me what the "\" being added is
> for or supposed to do?
>
lintian is a pretty helpful tool.
I: open-iscsi: h
On 02/25/2010 01:55 AM, Ritesh Raj Sarraf wrote:
From: Ritesh Raj Sarraf
Thanks for the patches. Could you tell me what the "\" being added is
for or supposed to do?
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send
On 02/25/2010 01:55 AM, Ritesh Raj Sarraf wrote:
From: Ritesh Raj Sarraf
Looks good. Thanks!
--
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 this group, sen
On Thu, Feb 25, 2010 at 03:26:57PM +0100, Jörg Delker wrote:
> Hi Pasi,
>
> could you please explain or give a hint on how to do that - limiting the
> target to a single initiator?
>
> My impression was, that this isn't possible with open-iscsi !?
>
You can't do that with open-iscsi. open-iscsi
On 02/25/2010 01:37 PM, Ritesh Raj Sarraf wrote:
Hello Mike,
On Friday 26 Feb 2010 00:24:29 Mike Christie wrote:
On 02/25/2010 01:55 AM, Ritesh Raj Sarraf wrote:
From: Ritesh Raj Sarraf
Thanks for the patches. Could you tell me what the "\" being added is
for or supposed to do?
lintian is
Hey all,
I'm running open-iscsi-2.0-865.9 on kernel-2.6.22. On bootup my
root drive is /dev/sda and I have a flash drive on /dev/sdc. When I
try to login to my iscsi device with mdadm I get a kernel oops:
-bash# iscsiadm -m node -p 172.19.151.169:3260,1 -T iqn.
1999-02.com.nexsan:p0:satabo
On 02/25/2010 06:03 AM, Or Gerlitz wrote:
Mike Christie wrote:
I am fine with either. The netdev name (ethX) also has the same problems
where udev can change it. It is there for aliases or vlans where we
cannot use hwaddress since multiple netdevs have the same MAC.
yes, correct both netdevice
On 02/25/2010 11:24 PM, Mike Christie wrote:
All in all, when non default interface is needed/used (e.g for
multipathing), I am quite sure we need to have some sort of source ip
for iser in ep_connect, please let me know what you think would be the
easy/best or close to either of (...) way to hav
On 02/25/2010 07:20 AM, Or Gerlitz wrote:
Mike Christie wrote:
The nop watch dog is more of generic catch all problems. I think I was
saying offlist that iscsi_tcp is not able to detect many transport
problems quickly. For example if you just pulled a cable somewhere in
the network, iscsi_tcp ma
12 matches
Mail list logo