search for: cv_wait_sig

Author: owenr Repository: /hg/zfs-crypto/gate Revision: 492ae9b21637b4b4c3e19d1556772aae3284a6f8 Log message: 4316952 ufs_fault_v should not attempt to queue more then 1 handler for a failure event 6350587 threads blocked in cv_wait_sig after a "forced" unmount on error never woken up Files: update: usr/src/uts/common/fs/ufs/ufs_lockfs.c update: usr/src/uts/common/fs/ufs/ufs_panic.c

Hi, I am profiling some workloads for the voluntary and involuntary context switches. I am interested in finding out the reasons causing these two types of context switches. As far as I understand, involuntary context switch happens on expiration of time slice or when a higher priority process comes in. While the voluntary switch generally happens when a process is waiting for I/O etc. So to

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org