We are currently running open iscsi version 2.0-871 on RHEL 5.3 (2.6.18-92.1.6.0.2.el5) against a Dell Equallogic iScsi SAN group (firmware 4.3.5)
During some routine member volume operaions (moving volumes from one member to another) we had a strange error in /var/log/messages indicating that the mounted volume would be mounted read only. This is strange, becasue the array requested a logout/and re-logged in within 3 seconds, which should be well below the iscsi settings to return an error to the SCSI subsystem. Our vendor (Dell/Equallogic) does not recommend adjusting any settings in iscsid.conf so we are running all the defaults I am interested in this configuration option. "node.session.iscsi.FastAbort = No" which is disabled by default, but it is mentioned that it can be beneficial for Equallogic. Can anyone else using Equallogic comment if this option has increased stability during volume operations such as moving volumes between storage pools/arrays >From the default iscsid.conf: #************ # Workarounds #************ # Some targets like IET prefer after an initiator has sent a task # management function like an ABORT TASK or LOGICAL UNIT RESET, that # it does not respond to PDUs like R2Ts. To enable this behavior uncomment # the following line (The default behavior is Yes): node.session.iscsi.FastAbort = Yes # Some targets like Equalogic prefer that after an initiator has sent # a task management function like an ABORT TASK or LOGICAL UNIT RESET, that # it continue to respond to R2Ts. To enable this uncomment this line # node.session.iscsi.FastAbort = No Logs below: View from iscsi san: INFO 4/18/10 11:18:11 AM SATA01 iSCSI session to target '10.30.0.84:3260, iqn.2001-05.com.equallogic: 6-8a0900-540e73901-9410003608347990-disk2' from initiator '10.30.0.225:16261, iqn.1994-05.com.redhat:ec43807e8964' was closed. Logout request was received from the initiator. INFO 4/18/10 11:18:15 AM SATA01 iSCSI login to target '10.30.0.52:3260, iqn.2001-05.com.equallogic: 6-8a0900-540e73901-9410003608347990-disk2' from initiator '10.30.0.225:51784, iqn.1994-05.com.redhat:ec43807e8964' successful, using Jumbo Frame length. View from linux var/log/messages Apr 18 11:18:11 serv02 kernel: sd 24:0:0:0: SCSI error: return code = 0x00070000 Apr 18 11:18:11 serv02 kernel: end_request: I/O error, dev sdt, sector 27424 Apr 18 11:18:11 serv02 kernel: sd 24:0:0:0: SCSI error: return code = 0x00070000 Apr 18 11:18:11 serv02 kernel: end_request: I/O error, dev sdt, sector 27520 Apr 18 11:18:11 serv02 kernel: Buffer I/O error on device sdt1, logical block 3436 Apr 18 11:18:11 serv02 kernel: lost page write due to I/O error on sdt1 Apr 18 11:18:11 serv02 kernel: Aborting journal on device sdt1. Apr 18 11:18:11 serv02 kernel: ext3_abort called. Apr 18 11:18:11 serv02 kernel: EXT3-fs error (device sdt1): ext3_journal_start_sb: Detected aborted journal Apr 18 11:18:11 serv02 kernel: Remounting filesystem read-only Apr 18 11:18:12 serv02 iscsid: Target requests logout within 3 seconds for connection Apr 18 11:18:16 serv02 iscsid: connection22:0 is operational after recovery (1 attempts) -- 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, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
