Re: iSCSI initiator lockups
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In our last exciting episode, Danny Braniss (da...@cs.huji.ac.il) said: I guess it's time to fix this. danny Thank you very much for the pointer to the newer version; we have seen a=20 marked improvement with none of the 30 second studdering. I appreciate your rapid assistance! Good, can you send me the info of the target/s you are using to add to the list of supported targets? Cheers, danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iSCSI initiator lockups
--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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iSCSI initiator
Please clarify these : (1) Is iSCSI initiator not currently implemented for FreeBSD ? no idea. (2) There is no iSCSI target daemon currently ? /usr/ports/net/iscsi-target unless you HAVE to interwork with iSCSI, use ggate. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: iSCSI initiator
Please clarify these : (1) Is iSCSI initiator not currently implemented for FreeBSD ? (2) There is no iSCSI target daemon currently ? Check this post, it has step by step instructions for 6.x: http://www.southernledger.com/blogs/ee99ee/?p=33 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator
* Onkar [EMAIL PROTECTED] [05-16-2008]: (1) Is iSCSI initiator not currently implemented for FreeBSD ? http://www.freebsd.org/releases/7.0R/announce.html (2) There is no iSCSI target daemon currently ? net/iscsi-target -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator
Sahil Tandon wrote: * Onkar [EMAIL PROTECTED] [05-16-2008]: (1) Is iSCSI initiator not currently implemented for FreeBSD ? http://www.freebsd.org/releases/7.0R/announce.html (2) There is no iSCSI target daemon currently ? net/iscsi-target Onkar, you may also find this helpful. http://conshell.net/wiki/index.php/User:Fostermarkd/FreeBSD/iSCSI -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]