Date: Tue, 10 Mar 2009 14:00:14 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: jtn@jtn.cx Cc: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org Subject: Re: iSCSI initiator lockups Message-ID: <E1Lh0d4-0007UV-EX@kabab.cs.huji.ac.il> In-Reply-To: <20090309212720.GA49294@jtn.cx> References: <20090309212720.GA49294@jtn.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> > --ikeVEW9yuYc//A+q > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > I'm running into some odd headaches regarding what looks like iSCSI initiat= > ors > going to sleep for approximately 30 seconds before returning to life and > pumping a ton of information back to the target. While this is happening, > system load climbs up alarmingly fast. Looking at tcpdumps in Wireshark, it > shows what appears to be a nearly exact 30 second delay where the initiator > stops talking to the target server, then abruptly restarts. Currently > 8 machines are talking to 2 servers with 4 targets a piece, and while its= > =20 > working, we get good throughput. Activity is moderately high, as we are=20 > using the iSCSI targets as spool disks in an email cluster. As it appears > that iscsi-target is a single-threaded process, would it be valuable to > put each target in its own process on its own port? At any rate, this is > causing serious problems on the mail processing machines. > can you send me the output of sysctl net.iscsi chears, danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Lh0d4-0007UV-EX>