On 12/28/2012 01:25 PM, Amit wrote: > Hello, > > I am getting the following error on LIO target on kernel 3.6.9: > > Dec 28 19:19:36 localhost kernel: [84675.936068] tcp_sendpage() failure: 2184 > Dec 28 19:20:25 localhost kernel: [84724.832042] tcp_sendpage() failure: 3120 > Dec 28 19:21:14 localhost kernel: [84773.728078] tcp_sendpage() failure: 3080 > > On the initiator side, I get the following error that corresponds to the > above errors. As soon as the above tcp_sendpage() error occurs, the > following error appears on the initiator: > > [84946.834466] connection1:0: detected conn error (1020)
If you see the above sendpage error on the target and only see a conn error 1020 on the initiator side, then it might be the target got a failure during a send operation and dropped the connection. 1020 on the initiator side indicates the target dropped the tcp/ip connection. > [84947.085096] session1: __iscsi_block_session: Blocking session > [84947.085112] session1: __iscsi_block_session: Completed SCSI target > blocking > [84950.841261] session1: __iscsi_unblock_session: Unblocking session > [84950.841289] session1: __iscsi_unblock_session: Completed unblocking > session > [84950.841300] session1: iscsi_user_scan_session: Scanning session > [84950.849063] session1: iscsi_user_scan_session: Completed session scan > [84995.732106] connection1:0: detected conn error (1020) > [84995.982558] session1: __iscsi_block_session: Blocking session > [84995.982574] session1: __iscsi_block_session: Completed SCSI target > blocking > [84999.738920] session1: __iscsi_unblock_session: Unblocking session > [84999.738948] session1: __iscsi_unblock_session: Completed unblocking > session > [84999.738958] session1: iscsi_user_scan_session: Scanning session > [84999.749148] session1: iscsi_user_scan_session: Completed session scan > [85044.632438] connection1:0: detected conn error (1020) > [85044.882888] session1: __iscsi_block_session: Blocking session > [85044.882903] session1: __iscsi_block_session: Completed SCSI target > blocking > [85048.639086] session1: __iscsi_unblock_session: Unblocking session > [85048.639116] session1: __iscsi_unblock_session: Completed unblocking > session > [85048.639126] session1: iscsi_user_scan_session: Scanning session > [85048.649161] session1: iscsi_user_scan_session: Completed session scan > > This is during a aio operation. The error messages seem harmless as the > copy operation proceeds as expected. Are there any settings I can Ok. It seems the connection was dropped and the initiator was able to relogin and continue IO. > configure to reduce the number of occurrences of these errors? They seem If the problem is the target dropping the connection because it could not send IO, then I am not sure. You might be sending more IO than the target can handle and in that case you can lower the targets per session queue depth if LIO has a setting like that. If not then on the initiator side you can lower it by setting node.session.cmds_max lower. To set that either set it in iscsid.conf then rediscover the target and relogin or run iscsiadm -m node -o update to update it for specific targets already setup then relogin (probably also want to set it in iscsid.conf for future targets/portals too if it works). > to happen every few minutes. This is over a 100Mbps local network. > > Thanks, > Amit > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
