, Alex Zeffertt alex.zeffe...@eu.citrix.com
mailto:alex.zeffe...@eu.citrix.com wrote:
Yes, I've done it!
multipathd uses /sbin/scsi_id to determine which block devices are
really the same as eachother. (Actually, the callout is configured in
/etc/multipath.conf, but its usually /sbin/scsi_id
Yes, I've done it!
multipathd uses /sbin/scsi_id to determine which block devices are really the
same as eachother. (Actually, the callout is configured in /etc/multipath.conf,
but its usually /sbin/scsi_id).
If /sbin/scsi_id returns the same ID for two block devices then you should be
Mike Christie wrote:
On 03/15/2010 05:56 AM, Alex Zeffertt wrote:
The bugzilla ticket requests a merge of two git commits, but neither of
those contain the libiscsi.c change that addresses bug #2. Was this a
mistake, or did you deliberately omit that part of your
speed-up-conn-fail-take3.patch
Mike Christie wrote:
On 03/07/2010 07:46 AM, Pasi Kärkkäinen wrote:
On Fri, Mar 05, 2010 at 05:07:53AM -0600, Mike Christie wrote:
On 03/01/2010 08:53 PM, Mike Christie wrote:
On 03/01/2010 12:06 PM, bet wrote:
1. Based on my timeouts I would think that my session would time out
Yes. It
xebech wrote:
Hello,
I am a new user of open-iscsi. I use iscsi to create diskless cluster.
I have a problem when I halt my nodes, I can not disconnect properly
my iscsi session from nodes because they need to access to their root
FS.
Do you know a method to properly halt diskless nodes ?
Hi
Hannes Reinecke wrote:
Mike Christie wrote:
On 01/07/2010 08:16 AM, Alex Zeffertt wrote:
Mike Christie wrote:
Thanks for doing this. Sorry for the late reply.
Just one comment on the patch. Could you move the code in the 'n' case
+ case 'n':
+ /*
+ * Bring up NICs required by targets
Mike Christie wrote:
Thanks for doing this. Sorry for the late reply.
Just one comment on the patch. Could you move the code in the 'n' case
+ case 'n':
+ /*
+* Bring up NICs required by targets in iBFT
+*
[...]
some script to set up the net. But if they like the iscsi tools to do
this for them, then rebase your patch so we can merge it.
Hi Mike, Thanks for your reply. I'll rebase the patch and send it on
when I get back to work in the new year.
I think it's unlikely that RH initrds will
Mike Christie wrote:
Alex Zeffertt wrote:
Mike Christie wrote:
Alex Zeffertt wrote:
Please could the attached patch be considered for inclusion in the
open-iscsi
source.
Regards,
Alex Zeffertt
Changelog:
-
iSCSI Boot Firmware Tables are able to specify up to two iSCSI
All,
Please ignore the patch in my previous email and use the one attached instead.
I fixed a bug in the previous patch where iscsistart -n was assuming that the
interface being configured was already up.
Regards,
Alex
Alex Zeffertt wrote:
Please could the attached patch be considered
Mike Christie wrote:
Alex Zeffertt wrote:
Please could the attached patch be considered for inclusion in the
open-iscsi
source.
Regards,
Alex Zeffertt
Changelog:
-
iSCSI Boot Firmware Tables are able to specify up to two iSCSI targets, but
until now open-iscsi has only
Please could the attached patch be considered for inclusion in the open-iscsi
source.
Regards,
Alex Zeffertt
Changelog:
-
iSCSI Boot Firmware Tables are able to specify up to two iSCSI targets, but
until now open-iscsi has only been able to display/attach one of these.
This change
12 matches
Mail list logo