Date: Wed, 10 Mar 2010 18:46:12 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Kevin Day <toasty@dragondata.com> Cc: freebsd-fs@freebsd.org Subject: Re: iscsi over HAST backed storage partial success Message-ID: <20100310174612.GF1715@garage.freebsd.pl> In-Reply-To: <7418ECC2-55C1-4A28-82EA-0972AFE745EF@dragondata.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Mar 09, 2010 at 05:03:41PM -0600, Kevin Day wrote: > > I'm running istgt (iscsi target) using HAST backed storage. For the most part, it seems to work really well. I have ucarp running to change the IP that istgt is bound to, and modified the ucarp scripts to start/stop istgt depending on which side is the master. If I shut down the primary, the secondary takes over and all seems well. > > However, if I reboot the secondary, the primary starts freezing up for long periods: > > Mar 9 22:46:27 cs04 hastd: [iscsi1] (primary) Unable to r: Socket is not connected. > Mar 9 22:46:27 cs04 hastd: [iscsi1] (primary) Unable to co: Connection refused. > Mar 9 22:46:42 cs04 last message repeated 3 times > Mar 9 22:46:53 cs04 istgt[14298]: ABORT_TASK > Mar 9 22:47:35 cs04 last message repeated 3 times > Mar 9 22:48:02 cs04 hastd: [iscsi1] (primary) Unable to co: Operation timed out. > Mar 9 22:48:02 cs04 istgt[14298]: CmdSN(45748), OP=0x2a, ElapsedTime=74 cleared > Mar 9 22:48:02 cs04 istgt[14298]: istgt_iscsi.c: 640:istgt_iscsi_write_pdu: ***ERROR*** iscsi_write() failed (errno=32) > Mar 9 22:48:02 cs04 istgt[14298]: istgt_iscsi.c:3327:istgt_iscsi_op_task: ***ERROR*** iscsi_write_pdu() failed > Mar 9 22:48:02 cs04 istgt[14298]: istgt_iscsi.c:3867:istgt_iscsi_execute: ***ERROR*** iscsi_op_task() failed > Mar 9 22:48:02 cs04 istgt[14298]: istgt_iscsi.c:4337:worker: ***ERROR*** iscsi_execute() failed > Mar 9 22:48:02 cs04 istgt[14298]: CmdSN(490802), OP=0x2a, ElapsedTime=73 cleared > Mar 9 22:48:02 cs04 istgt[14298]: CmdSN(28387), OP=0x2a, ElapsedTime=73 cleared > Mar 9 22:48:14 cs04 istgt[14298]: ABORT_TASK > Mar 9 22:48:52 cs04 last message repeated 2 times > Mar 9 22:49:22 cs04 hastd: [iscsi1] (primary) Unable to co: Operation timed out. > > As soon as the secondary comes back online, everything starts behaving again and all is well. > > Is this expected behavior at this point, or should hastd not block like this? It shouldn't of course block like this. There is a separate thread responsible for reconnecting which shouldn't interact with I/O threads. I'll try to reproduce and will let you know. -- Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuX2uMACgkQForvXbEpPzT7ewCgu70tq0+kx0OyRe4PQAaR1HV3 KAsAn2mW+sMKaLvKpvfJWILmNUiQfYX6 =ONha -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100310174612.GF1715>