Carson Gaspar wrote:
Carson Gaspar wrote:
I'll also note that the kernel is certainly doing _something_ with my
pool... from "iostat -n -x 5":
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
40.5 5.4 1546.4 0.0 0.0 0.3 0.0 7.5 0 19 c7t0d0
40.5 5.4 1546.4 0.0 0.0 0.6 0.0 12.1 0 31 c7t1d0
44.1 5.8 1660.8 0.0 0.0 0.4 0.0 7.6 0 21 c7t2d0
41.9 5.4 1546.4 0.0 0.0 0.3 0.0 6.6 0 22 c7t3d0
40.7 5.8 1546.4 0.0 0.0 0.5 0.0 9.9 0 25 c7t4d0
40.3 5.4 1546.4 0.0 0.0 0.4 0.0 8.5 0 20 c7t6d0
40.5 5.4 1546.4 0.0 0.0 0.4 0.0 7.9 0 23 c7t7d0
And now I know what:
bash-3.2# pgrep zfsdle | wc
15198 15198 86454
bash-3.2# uname -a
SunOS gandalf.taltos.org 5.11 snv_118 i86pc i386 i86xpv
I see a few other folks reporting this, but no responses.
I don't see any bugs filed against this, but I know the search engine is
"differently coded"...
And they have all been spawned by:
bash-3.2# ps -fp 991
UID PID PPID C STIME TTY TIME CMD
root 991 1 1 15:30:40 ? 1:50
/usr/lib/sysevent/syseventconfd
I renamed /etc/sysevent/config/SUNW,EC_dev_status,ESC_dev_dle,sysevent.conf and
restarted syseventd to stop the madness.
Anyone know what has gone so horribly wrong?
The other reports I've seen were against snv_123, so the current release appears
to have the same bug.
--
Carson
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
