corruption in session list
From time to time, I see errors like the following when I run 'iscsiadm -m session': tcp: [2] []:-1,1 ��A�¹V��� Is it a known bug? I don't know how to reproduce it. It just happens. Thanks, Erez --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsiadm version 2.0-868 incompatibility with older version
Ulrich Windl wrote:
Hi,
SLES10 SP2 ships iscsiadm version 2.0-868, while SP1 had an older version.
For
SP1 I used the following command to set all discovered nodes to auto-login:
for sid in $(iscsiadm -m node | awk '{gsub(/^\[/, ); gsub(/\]/, ); print
$1 }'
| sort)
Is this just going to get the sid for all the records? If so then I
think you can do
iscsiadm -m node -o update
This will update the setting for all records.
do
iscsiadm -m node -r $sid -o update -n node.startup -v automatic
done
What would be the equivalent for the newer version that says: iscsiadm: node
mode: option '-r' is not allowed/supported?
To change just one record you can do:
iscsiadm -m node -T target -p ip -o update
or if you want to manipulate records using the sid of running sessions
you can do
iscsidm -m session -r $sid -o update .
--~--~-~--~~~---~--~~
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 this group, send email to
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
Re: Persistent connections across initiator reboot
HIMANSHU wrote: I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and performed the steps mentioned in my last post. Still after when I discover using 'iscsiadm -m discovery -t sendtargets -p 192.168.30.12 -o new -o delete',nodes and sendtargets entries gets overwritten. Sorry, sorry, my fault. I was looking up the current devel version. In RHEL 5.3/CentO35.3 and below there is no fix. You have to use the upstream code. I can also give you a test src rpm I am working on for RHEL 5.4/CentOs 5.4 if you want? It has the change needed. --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsid : mgmt_ipc_write_rsp: rsp to fd 5
[~] # iscsiadm -m discovery -d 8 -t sendtargets -p 192.168.1.79:3260 iscsiadm: ip 192.168.1.79, port 3260, tgpt -1 iscsiadm: Max file limits 1024 1024 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 Could you do iscsiadm -m discovery -d 8 -t sendtargets -p 192.168.1.79:3260 -d 8 and send all that output? --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: corruption in session list
Erez Zilber wrote: From time to time, I see errors like the following when I run 'iscsiadm -m session': tcp: [2] []:-1,1 ��A�¹V��� Is it a known bug? I don't know how to reproduce it. It just happens. I have not seen it. Have you seen it in multiple versions of open-iscsi? Do you actually have a session with sid 2 running or is it all garbage? --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
gcc warning at iscsi_add_session
drivers/scsi/scsi_transport_iscsi.c: In function 'iscsi_add_session': drivers/scsi/scsi_transport_iscsi.c:678: warning: 'err' may be used uninitialized in this function Hi mike, what ever happened to the fix of above warning? I'm sure I saw a fix in the mailing list but it never made it into mainline (2.6.30-rc3) Has it been dropped? Thanks Boaz --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: gcc warning at iscsi_add_session
Boaz Harrosh wrote: drivers/scsi/scsi_transport_iscsi.c: In function 'iscsi_add_session': drivers/scsi/scsi_transport_iscsi.c:678: warning: 'err' may be used uninitialized in this function Hi mike, what ever happened to the fix of above warning? I'm sure I saw a fix in the mailing list but it never made it into mainline (2.6.30-rc3) I was going to change to handle a issue Andrew had brought up. --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
strange behavior on kernel update
Hi, i'm using centos with dm-multipath and iscsi as a database system. All packages are normal centos packages from their mirrors. This night I was updating centos to the current release (5.3, previous version was 5.2). So the first thing I have done was stopping the multipathd and iscsi. After this I was doing the normal update stuff (yum check-updates, yum clean all, yum update glibc\*, yum update). During the last yum update the new kernel was installed (2.6.18-128.1.6.el5, previous was 2.6.18-92.1.22.el5). During the installation process of the kernel, the yum process hangs. Looking with ps for the hanging processes, I see that the kernel package was building the initrd. After killing this process and repeating the yum update process (this time only the kernel-package) about 5 times, the same strange failure occurs (process hangs on building initrd). The sixth time I was stracing the whole update process and see that the mkinitrd process does a wait-syscall for sth.. After killing this process again I went down to the server room to reboot the system and try another update process. I reboot the systems, stops multipathd and iscsi and starting the update process. On this update I could see that during the mkinitrd process, a kernel message device-mapper: failed path x:x:x:x occurs. Hmm this is strange I thought, because I've stopped multipathd and iscsi, so why means the kernel that a path is failed? Once again killing the mkinitrd process and then starting multipathd and iscsi I've tried another update process. And, yeha, it works??? I could reproduce this behavior on 2 machines, both centos with standard packages. So can anybody comprehend this failure or any ideas? Cheers Maddin --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Tuning iscsi read performance with multipath Redhat 5.3 / SLES 10 SP2 / Oracle Linux / Equallogic
I'm not sure if you have seen this, but there is a guide from Dell on
this subject:
http://www.support.dell.com/support/edocs/software/appora10/lin_x86_64/multlang/EELinux_storage_4_1.pdf
Also I would suggest the following changes in multipath.conf for RHEL5
device {
vendor EQLOGIC
product 100E-00
getuid_callout /sbin/scsi_id -g -u -s /block/%n
hardware_handler 0
path_selector round-robin 0
path_grouping_policy multibus
failback immediate
features 1 queue_if_no_path
path_checker tur
rr_min_io 10
rr_weight uniform
}
Byte
--~--~-~--~~~---~--~~
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 this group, send email to
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
Re: Persistent connections across initiator reboot
Thank you very much Mike for all this. Can you please give me the test src rpm for CentOS 5.4? On Apr 27, 8:50 pm, Mike Christie micha...@cs.wisc.edu wrote: HIMANSHU wrote: I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and performed the steps mentioned in my last post. Still after when I discover using 'iscsiadm -m discovery -t sendtargets -p 192.168.30.12 -o new -o delete',nodes and sendtargets entries gets overwritten. Sorry, sorry, my fault. I was looking up the current devel version. In RHEL 5.3/CentO35.3 and below there is no fix. You have to use the upstream code. I can also give you a test src rpm I am working on for RHEL 5.4/CentOs 5.4 if you want? It has the change needed. --~--~-~--~~~---~--~~ 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 this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
