Re: iSCSI: NetBSD-9 target, Linux initiator

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

However, admittedly - on a -current machine with one NVMM NetBSD guest
running atf tests (NVMM has been flaky for me since qemu 4.2), my
istgt daemon appears stuck - and the long operation failed:
....
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] acpitz3: workqueue
busy: updates stopped
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] acpitz7: workqueue
busy: updates stopped
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] coretemp0: workqueue
busy: updates stopped
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] coretemp1: workqueue
busy: updates stopped
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] coretemp2: workqueue
busy: updates stopped
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] coretemp3: workqueue
busy: updates stopped
Feb 21 21:07:25 ymir /netbsd: [ 113606.3193243] acpibat0: workqueue
busy: updates stopped
Feb 21 21:08:01 ymir istgt[22300]: LOGICAL_UNIT_RESET
Feb 21 21:16:24 ymir istgt[22300]:
istgt_lu_disk.c:5331:istgt_lu_disk_queue_start: ***ERROR*** timeout
trans_cond CmdSN=153610 (time=30)
Feb 21 21:16:24 ymir istgt[22300]: istgt_lu.c:3262:luworker:
***ERROR*** LU1: lu_disk_queue_start() failed
.....

On Fri, 21 Feb 2020 at 21:03, Michael van Elst <mlelstv%serpens.de@localhost> wrote:
>
> On Fri, Feb 21, 2020 at 07:46:26PM +0100, BERTRAND Joel wrote:
> > > In my experience the iscsi target (and the userland iscsi initiator)
> > > are pretty limited and somewhat broken. I suggest you use the
> > > iscsi target from pkgsrc (net/istgt). Much better, faster and more
> > > compatible.
> >
> >       Same configuration files or not ?
>
> Unfortunately not.
>
> --
>                                 Michael van Elst
> Internet: mlelstv%serpens.de@localhost
>                                 "A potential Snark may lurk in every tree."



-- 
----