Date: Mon, 5 Dec 2011 20:21:56 +0100 From: Mark Martinec <Mark.Martinec+freebsd@ijs.si> To: freebsd-current@freebsd.org Subject: Re: iSCSI initiator: iscontrol cannot be stopped or killed Message-ID: <201112052021.56138.Mark.Martinec%2Bfreebsd@ijs.si> In-Reply-To: <4ED415CD.1080005@delphij.net> References: <201111240126.21470.Mark.Martinec%2Bfreebsd@ijs.si> <4ED415CD.1080005@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Xin LI wrote: > Try procstat -kk <pid> to find the calling stack, as a start? > This could be very useful when tracking down problems. > Also the 'D' flag from ps(1) output in most times are not quite useful > and ps -o wchan would tell you what exactly it was waiting for, just FYI. Posted both a few days ago, you must have missed it. Ivan Voras wrote: > You should probably ask at the freebsd-scsi@ mailing list. From looking > at the code it looks like "ffp" is used for LUN scan timeout. Done, posted to freebsd-scsi@ mailing list. Thanks for the suggestion. Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112052021.56138.Mark.Martinec%2Bfreebsd>