RE: 3.12.5 Target Errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Updated to 3.12.19, applied the patches... See below.We keep losing targets on the vmware initiator side. And see the dmesg below.  We do not use authentication on the iscsi side.


[  134.501339] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.506549] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.511110] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.515427] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.519958] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.524221] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.529635] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  134.532997] MODE SENSE: unimplemented page/subpage: 0x1c/0x02
[  615.245882] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.249698] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.253704] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.257561] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.265030] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.268861] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.272712] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.276589] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.280143] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.284150] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.288042] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.291777] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.295679] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.299590] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.303497] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[  615.307360] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
[ 1533.095556] Unknown RDMA CMA event: 15
[ 1533.854793] Unknown RDMA CMA event: 15
[ 1534.606031] Unknown RDMA CMA event: 15
[ 1534.606039] Unknown RDMA CMA event: 15
[ 1543.205637] Unknown RDMA CMA event: 15
[ 1548.872095] iSCSI Login timeout on Network Portal 192.168.252.101:3271
[ 1549.031925] Unknown RDMA CMA event: 15
[ 1549.639350] iSCSI Login timeout on Network Portal 192.168.252.101:3270
[ 1550.406595] iSCSI Login timeout on Network Portal 192.168.252.101:3274
[ 1550.406616] iSCSI Login timeout on Network Portal 192.168.251.101:3262
[ 1550.406648] iSCSI Login negotiation failed.
[ 1551.173836] iSCSI Login timeout on Network Portal 192.168.251.101:3260
[ 1565.431904] iSCSI Login timeout on Network Portal 192.168.252.101:3274
[ 1565.431957] iSCSI Login negotiation failed.
[ 1598.273720] iSCSI Login negotiation failed.
[ 1598.273721] iSCSI Login negotiation failed.
[ 1598.273757] iSCSI Login negotiation failed.
[ 1598.294593] Unknown RDMA CMA event: 8
[ 1598.361379] conn->conn_login is NULL
[ 1598.361383] CPU: 2 PID: 20 Comm: kworker/2:0 Tainted: GF            3.12.19+ #1
[ 1598.361385] Hardware name: Supermicro X9DRX+-F/X9DRX+-F, BIOS 3.00 07/09/2013
[ 1598.361392] Workqueue: isert_rx_wq isert_cq_rx_work [ib_isert]
[ 1598.361394]  ffff8803d6eb0000 ffff88046fab5d08 ffffffff81553ae7 0000000000000000
[ 1598.361398]  0000000000000000 ffff88046fab5d48 ffffffffa075e03d ffff88046fab5d88
[ 1598.361400]  ffff8803df5d3000 ffff8803d6eb0000 ffff88085fe00000 00000003d6eb0000
[ 1598.361403] Call Trace:
[ 1598.361408]  [<ffffffff81553ae7>] dump_stack+0x49/0x62
[ 1598.361411]  [<ffffffffa075e03d>] isert_rx_login_req+0x19d/0x1b0 [ib_isert]
[ 1598.361413]  [<ffffffffa075fab7>] isert_rx_completion+0x1d7/0x2a0 [ib_isert]
[ 1598.361416]  [<ffffffffa075fcab>] isert_cq_rx_work+0x12b/0x1b0 [ib_isert]
[ 1598.361419]  [<ffffffff810685a3>] process_one_work+0x183/0x490
[ 1598.361421]  [<ffffffff81069a7f>] worker_thread+0x11f/0x3a0
[ 1598.361423]  [<ffffffff81069960>] ? manage_workers+0x160/0x160
[ 1598.361426]  [<ffffffff8106f99e>] kthread+0xce/0xe0
[ 1598.361429]  [<ffffffff810baf84>] ? check_modinfo+0x174/0x190
[ 1598.361432]  [<ffffffff8106f8d0>] ? kthread_freezable_should_stop+0x70/0x70
[ 1598.361434]  [<ffffffff8156026c>] ret_from_fork+0x7c/0xb0
[ 1598.361436]  [<ffffffff8106f8d0>] ? kthread_freezable_should_stop+0x70/0x70
[ 1601.251093] iSCSI Login negotiation failed.
[ 1601.262977] Unknown RDMA CMA event: 8

> -----Original Message-----
> From: Nicholas A. Bellinger [mailto:nab@xxxxxxxxxxxxxxx]
> Sent: Thursday, May 15, 2014 3:22 PM
> To: Moussa Ba (moussaba)
> Cc: Sagi Grimberg; target-devel@xxxxxxxxxxxxxxx; Nicholas Bellinger; Or
> Gerlitz
> Subject: Re: 3.12.5 Target Errors
> 
> On Thu, 2014-05-15 at 21:21 +0000, Moussa Ba (moussaba) wrote:
> > Thanks Nick.  I just updated to 3.14.4, does that include the
> necessary patches?I don't have any particular requirement for version.
> 
> Minus the three fixes from Sagi that are queued in
> target-pending/master, v3.14.4 has all of the other iser-target related
> fixes.
> 
> You'll still want to apply these three mentioned earlier..
> 
> > More interested in functionality and stability.  3.14.4 generates the
> following error:
> >
> > [  271.008891] rdma_accept() failed with: -99
> > [  271.904227] rdma_accept() failed with: -99
> > [  271.933538] rdma_accept() failed with: -99
> >
> >
> 
> Mmmm, rdma_accept() is returning -EADDRNOTAVAIL here..
> 
> It appears that something is failing in drivers/infiniband/core/cma.c
> outside of ULP specific code..  (Or CC'ed).
> 
> Note that there was a userspace ABI version bump for libibverbs,
> libmlx4, and librdmacm during v3.14..  You might be hitting some of
> that
> related fallout here somehow..
> 
> > 8 of targets have disappeared from vmware 5.5, but they are present
> > and show enabled on the target.  Anyhow, what is the recommended
> > version for stability/functionality.
> 
> v3.12.19 with the 5 patches applied is probably the best bet here,
> until
> the -EADDRNOTAVAIL issue can be tracked down on v3.14.y.
> 
> --nab

��.n��������+%������w��{.n����j�����{ay�ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��





[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux