On 24/11/2011 18:06, Mark Martinec wrote: >>> If you can get it back into this state, >> >> Sure, *every* time. >> >>> a procstat -k -k<iscontrol pid> would be very helpful. >>> (the second -k is not a typo). >> >> # procstat -k -k 5896 >> PID TID COMM TDNAME KSTACK >> 5896 102364 iscontrol - mi_switch+0x174 >> sleepq_timedwait+0x42 _sleep+0x301 ic_init+0x2f1 iscsi_ioctl+0x525 >> devfs_ioctl_f+0x7b kern_ioctl+0x115 sys_ioctl+0xfd amd64_syscall+0x450 >> Xfast_syscall+0xf7 > > Additional info: the process is blocking on 'ffp', unresponsive to signals: > > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > 0 5896 1 0 20 0 16424 1264 ffp Ds ?? 0:00.04 iscontrol -c /etc/iscsi.conf -n xxx > You should probably ask at the freebsd-scsi_at_ mailing list. From looking at the code it looks like "ffp" is used for LUN scan timeout.Received on Mon Nov 28 2011 - 11:24:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:21 UTC