Displaying 5 results from an estimated 5 matches for "sys_syscall".
Did you mean:
sys_syscall32
2010 Jan 12
0
dmu_zfetch_find - lock contention?
...f_read+0x27a
zfs`dmu_buf_hold_array_by_dnode+0x287
zfs`dmu_buf_hold_array+0x81
zfs`dmu_read_uio+0x49
zfs`zfs_read+0x15e
zfs`zfs_shim_read+0xc
genunix`fop_read+0x31
genunix`read+0x188
unix`sys_syscall+0x17b
1861
unix`mutex_delay_default+0xc
unix`mutex_vector_enter+0x99
zfs`dmu_zfetch_find+0x1b8
zfs`dmu_zfetch+0xc9
zfs`dbuf_read+0x27a
zfs`dmu_buf_hold_array_by_dnode+0x287
zfs`dmu_buf_ho...
2006 Sep 22
1
Linux Dom0 <-> Solaris prepared Volume
...but need xen v3.0.2-3-sun
WARNING: The kernel may not function correctly
====
:
:
:
====
pseudo-device: pm0
pm0 is /pseudo/pm@0
pseudo-device: pool0
pool0 is /pseudo/pool@0
panic[cpu0]/thread=fffffffec48d8c00: stisti
>> warning! 8-byte aligned %fp = ffffff0001326fa8
ffffff0001326fa8 unix:sys_syscall+4c ()
syncing file systems... 2 2 done
skipping system dump - no dump device configured
rebooting...
panic after init started - SHUTDOWN_crashed
===SNAP===
I tried wit xen-unstable and xen-3.0.2-3
Compiled with gcc3.4 on Ubuntu
Someone an idea ?
THanks
Jan
2009 Apr 01
4
ZFS Locking Up periodically
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
2007 May 02
41
gzip compression throttles system?
I just had a quick play with gzip compression on a filesystem and the
result was the machine grinding to a halt while copying some large
(.wav) files to it from another filesystem in the same pool.
The system became very unresponsive, taking several seconds to echo
keystrokes. The box is a maxed out AMD QuadFX, so it should have plenty
of grunt for this.
Comments?
Ian
2010 Jun 28
23
zpool import hangs indefinitely (retry post in parts; too long?)
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