search for: turnstile_block

...sys_syscall32+0x101() Other zpool commands, df, format all waiting on a mutex lock spa_namespace_lock to release: PC: _resume_from_idle+0xf8 CMD: zpool status stack pointer for thread fffffe84d34b3ba0: fffffe8001439bf0 [ fffffe8001439bf0 _resume_from_idle+0xf8() ] swtch+0x110() turnstile_block+0x1fb() mutex_vector_enter+0x40f() spa_all_configs+0x48() zfs_ioc_pool_configs+0x20() zfsdev_ioctl+0x13e() cdev_ioctl+0x1d() spec_ioctl+0x50() fop_ioctl+0x25() ioctl+0xac() sys_syscall32+0x101() ========= PC: _resume_from_idle+0xf8 CMD: zpool list stack po...

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

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