Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Feb 2019 10:07:53 +0100
From:      peter.blok@bsd4all.org
To:        freebsd-scsi@freebsd.org
Cc:        mav@freebsd.org
Subject:   Re: iSCSI stall
Message-ID:  <6329694E-4BF7-4467-A3A7-2556AA0C3FD6@bsd4all.org>
In-Reply-To: <3579EC93-825D-4908-B177-673363111BEF@bsd4all.org>
References:  <3579EC93-825D-4908-B177-673363111BEF@bsd4all.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

Did not get any response on this, but it seems the commits 344072, =
344075 and 344076 have fixed the issue. My assumption is that the target =
doesn=E2=80=99t handle re-ordering with non-offset CDBs very well.

Normally every time when the backup (zfs recv on target) ran, it hung a =
couple of times and now it went thru without a glitch and without any =
quirks.

Peter


> On 16 Jan 2019, at 10:05, peter.blok@bsd4all.org wrote:
>=20
> Hi,
>=20
> I have a ReadyNAS RND4000 as an iSCSI target. The target is the only =
device in a ZFS pool and is receiving backups thru zfs receive. The =
initiator is FreeBSD 11.x (recent stable at this moment), but this =
probably happens with 12.0 as well.
>=20
> During a zfs receive it stalls. Nothing happens anymore. When I send a =
TUR via camcontrol everything continues. Any other target on any other =
platform works fine.
>=20
> When I take a network trace it looks as if it is around SYNCHRONIZE =
CACHE. If this takes too long in the target and before the reply is back =
some new READ CDBs are send, it seems to hang only showing Nop-In and =
Nop-out. The moment I send a TUR it continues replying with the data of =
the READs that were owed.
>=20
> It is not a big deal, but it irritates me and I would like to create a =
work-around for this, assuming it is caused by the target and there is =
probably no way to fix it there. One test was to create a quirk to =
reduce the tags to 1, but that didn=E2=80=99t help. Although it is 1 it =
still seems to send multiple CDB concurrently.
>=20
> In the past I have attempted to port FreeBSD to the ReadyNAS, but got =
stuck on fan control. I wasn=E2=80=99t able to control the fan and it =
made too much noise. I was able to get the network up and running.
>=20
> Any tips?
>=20
>=20
>=20
>=20
> _______________________________________________
> freebsd-scsi@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to =
"freebsd-scsi-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6329694E-4BF7-4467-A3A7-2556AA0C3FD6>