Hi Jun, On Mon, 2014-04-28 at 15:29 -0700, Jun Wu wrote: > Hi Nicholas, > > I am reporting another bug. The setup is similar to the one I > described in "tcm_fc crash" email. > I think your broken build process is causing these random bugs. Please retry using the proper upstream build process so that the target modules are not reported as '(O)ut of tree' or '(F)orcibly loaded'. Thanks, --nab > One initiator connects to a target through fcoe vn2vn. Run dd > if=/dev/zero of=/dev/sdi bs=1M & from the initiator to a SSD drive on > the target. The following message is printed out on the target: > > Apr 26 22:16:13 poc2 kernel: [ 7265.516903] ft_recv_write_data: xid > 0xe4, f_ctl 0x8, cmd->sg ffff88032cafb800, cmd->sg_cnt 0x10. DDP was > setup hence not expected to receive frame with payload, Frame will be > dropped if'Sequence Initiative' bit in f_ctl isnot set > > In the meantime, on the initiator side, IO hangs for a while (about 30 > seconds) according to iostat's result. > > In the above dd command, bs=4K can also trigger the message. > > The issue is easy to reproduce with iblock, fileio, or pscsi. When it > happens, the targetcli configuration can't be deleted after initiator > io has stopped. > > I am using Ubuntu 14.04. > > root@poc2:~# uname -a > Linux poc2 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC > 2014 x86_64 x86_64 x86_64 GNU/Linux > > Thanks, > > Jun -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
