Well, aftr reboot I destroyed snapshots in nfs-s5-s8 and now system is working
ok without effects desribed before (at least so far).
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensol
System was booting over 30 minutes (it was staying hust after checkign for ufs
was done) - I can see on the array that disks in pool nfs-s5-s8 are blinking -
I guess it was hanging during zfs import/mount.
It was reported during ZFS beta and was supposed to be fixed - looks like it's
not.
T
Robert Milkowski wrote:
> I issued svcadm disable nfs/server
> nfsd is still there with about 1300 threads (down from 2052).
> stack pointer for thread 3002f4bd300: 2a1084b7021
> [ 02a1084b7021 cv_wait+0x40() ]
> 02a1084b70d1 exitlwps+0x11c(0, 20, 4202, 300116ec7e0, 10,
> 3
It's not only when I try to stop nfsd - during normall operations I see that
one CPU has 0% idle, all traffic is only to one pool (and this is very small
traffic) and all nfs threads hung - I guess all these threads are to this pool.
bash-3.00# zpool iostat 1
capacity operatio
I issued svcadm disable nfs/server
nfsd is still there with about 1300 threads (down from 2052).
mpstat show at least on CPU with 0% idle all the time and:
bash-3.00# dtrace -n fbt:::entry'{self->vt=vtimestamp;}' -n
fbt:::return'/self->vt/[EMAIL PROTECTED](vtimestamp-self->vt);self->vt=0;}' -n