On 11/07/17 10:51, 李春 wrote:
We have meet a problem of tgtd CPU 100%. the infinband network card was negotiate as eth mode by mistake, after we change it to ib mode and restart opensmd for correct State（Active） the tgtd using 100% of CPU. and when we connect to it using tgtadm, tgtadm hang forever. # how to repeat * tgtd export a disk throught port 3260 of iser * iscsiadm login a target from tgt through infiniband * connectx_port_config set the mellanox infiniband to eth mode * connectx_port_config set the mellanox infiniband to ib mode * /etc/init.d/opensmd restart * tgtadm connect to tgt will hang # error messge ``` Jul 1 21:32:37 shadow tgtd: iser_handle_rdmacm(1628) Unsupported event:11, RDMA_CM_EVENT_DEVICE_REMOVAL - ignored Jul 1 21:32:37 shadow tgtd: iser_handle_rdmacm(1628) Unsupported event:11, RDMA_CM_EVENT_DEVICE_REMOVAL - ignored Jul 1 21:32:39 shadow tgtd: iser_handle_async_event(3174) dev:mlx4_0 HCA evt: local catastrophic error
iser code in tgtd does not know how to correctly handle RDMA device removal events (and it never did). The event is generated from the port configuration step while tgt-iser is bound to it. Once the device is removed the device handle tgt-iser has is essentially unusable, which explains the qp creation failures below. Handling DEVICE_REMOVAL event handling is a new feature request.
Jul 1 21:46:56 shadow tgtd: iser_cm_connect_request(1471) conn:0x1380bf0 cm_id:0x1380950 rdma_create_qp failed, Cannot allocate memory Jul 1 21:46:56 shadow tgtd: iser_cm_connect_request(1520) cm_id:0x1380950 rdma_reject failed, Bad file descriptor Jul 1 21:46:56 shadow tgtd: iser_cm_connect_request(1471) conn:0x1380bf0 cm_id:0x1380950 rdma_create_qp failed, Cannot allocate memory
And also tgt-iser cannot even reject the (re)connect request.
Jul 1 21:46:56 shadow tgtd: iser_cm_connect_request(1520) cm_id:0x1380950 rdma_reject failed, Bad file descriptor ``
