t keeping a static list and not bother it any longer
- a.
On 6/4/08, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> Mike Christie wrote:
>> a s p a s i a wrote:
>>> Wanted to update on this issues again ...
>>>
>>>> It just means that userspace
iscsiadm -m session -P <1, 2 or 3> level
thanks again - I am running a script overnight to soak and see if any
networking hiccups would reproduce the symptoms now that I have
changed the timeout value ...
- a.
On 6/4/08, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> a s p a s i
,
- aspasia.
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
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
Wanted to update on this issues again ...
> It just means that userspace tried to set a feature the kernel did not
> support. It is not serious.
>
> If there was nothing before that first line about the kernel reporting a
> connection error, then the target could have initiated this. Do you see
>
ave any thoughts would be
greatly appreciated
thx,
- a.
On Fri, May 30, 2008 at 11:36 AM, a s p a s i a <[EMAIL PROTECTED]> wrote:
> h interesting!
>
> 1. so yeah, it did seem to error with grubby, BUT it exit 0'ed ...
>
> + /sbin/grubby --add-kernel=/boot/vmlinuz-2
1:0 is operational after
recovery (1 attempts)
... what id the -38 error code?
thanks in advance.
- a.
>
> >
>
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
h interesting!
1. so yeah, it did seem to error with grubby, BUT it exit 0'ed ...
+ /sbin/grubby --add-kernel=/boot/vmlinuz-2.6.18-53.1.21.el5xen
--initrd /boot/initrd-2.6.18-53.1.21.el5xen.img --copy-default --title
'CentOS (2.6.18-53.1.21.el5xen)' '--args=root=LABEL=iscsiRoot '
'--remove-
ments it passes to grubby. Could be that some of
> them are no good.
>
> >
>
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post t
oh ok .. i figured that I needed to create the record - so I did this:
iscsiadm -m node -T
iqn.2008-04.com.mycompany.lab:storage.centos51_x64_xen -p 192.168.17.3
-o new
New iSCSI node [tcp:[hw=default,ip=,net_if=default,iscsi_if=default]
192.168.17.3,3260,-1
iqn.2008-04.com.maxiscale.lab:storage.
de1 2015032 1861252 51420 98% /
[EMAIL PROTECTED] /]#
where /dev/sde1 is my iscsiroot ...
any thoughts?
>
> >
>
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
On Thu, May 29, 2008 at 2:47 PM, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
>
>
> See http://wpkg.org/Diskless_/_remote_boot_with_Open-iSCSI on how to
> make a custom initrd for iSCSI booting.
>
Hi Tomasz
I used those instructions for Debian based distros ... for centos the
mkinitrd was
Linux
[EMAIL PROTECTED] etc]#
... strange though bec. iscsistart works and they were generated from
same installation ....
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"
thanks for this final note/recommendation! .. i will do so .. have
deployed the golden image though and so far my engineering users have
not complained seems like they are happy with their iscsi root on
CentoS!
- a.
--~--~-~--~~~---~--~~
You received this message
> I need more to the log. The parts above this would tell me what happened.
OK, I will capture complete console log next time, sorry, but I
rebooted the couple of test boxes that had this
> node.session.timeo.replacement_timeout = 172800
> node.conn[0].timeo.noop_out_timeout = 0
> node.con
e release? Before I do, I'd like to know if the above
are known errors and why?
thanks in advance,
A.
>
>
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
> Are you using 869 and do you also see the nop out timeout messages or do
> you just see these connection error messages?
>
just the above connections errors...
865 version:
[EMAIL PROTECTED] ~]# iscsiadm -V
iscsiadm version 2.0-865
[EMAIL PROTECTED] ~]# iscsistart -v
iscsistart version 2.0-86
you are at risk).
>
> The updated package is here:
> http://www.open-iscsi.org/bits/open-iscsi-2.0-869.1.tar.gz
>
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
probe -q crc32c
6. Upon re-starting the iscsiadm command, I was able to login and
connect to disk!
thanks a lot!
- a.
--
A S P A S I A
. . . . . . . . . . ..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"o
> Don't you mean /etc/init.d/iscsid ?
YES! ... sorry ...
yes, /etc/init.d/iscsid or (in other flavors the script is -
/etc/rc.d/open-iscsi) ... does not seem to exist.
I also noticed the iscsi modules have not been installed.
Do I need to install the initiator-tools also?
- a.
--~--~--
id.conf
> #11,12c11,12
> #< INITIATORNAME=/etc/initiatorname.iscsi
> #< DAEMON=/usr/sbin/iscsid
> #---
> #> INITIATORNAME=/etc/iscsi/initiatorname.iscsi
> #> DAEMON=/sbin/iscsid
>
> > thanks in advance,
> >
> &g
>
> This is a known bug in Ubuntu Hardy.. I just hit it today also:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/218215
>
> Install the newer kernel from the hardy proposed-updates repository and it
> fixes the problem.
>
>
arrgh! u kidding .. me .. ok .. thanks for the heads up!
-
> is a little scary. It looks like you might have multiple versions of
> userspace running/installed (open-iscsi-2.0-865.15 and 2.0-869). That we
> do not support. Make sure you have one version of userspace installed
> (do whereis for iscsid, iscsiadm iscsistart to see if there are multiple
>
> Nice. Did you diverge much from the document or pretty much followed it
> step-by-step?
pretty much stuck by the logic of Tomas's script ... but obviously had
to add my own modules (so I also peeked inside the init script of a
normal Ubuntu install on the same HW platform to ensure that I'm
l
Root on Ubuntu .. I used the
following instructions as guide (which is based on his Debian servers)
http://wpkg.org/Diskless_/_remote_boot_with_Open-iSCSI#Downloads
key is to get your init script working according to the configuration you have..
- a.
24 matches
Mail list logo
