Many processes stuck in zfs
Pawel Jakub Dawidek
pjd at FreeBSD.org
Wed Mar 10 18:04:09 UTC 2010
On Wed, Mar 10, 2010 at 07:42:43PM +0200, Andriy Gapon wrote:
> on 10/03/2010 19:31 Pawel Jakub Dawidek said the following:
> > This should be impossible. If we are that deep in zfsvfs_teardown(), it means
> > that we hold the z_teardown_lock exclusively. And we do as 'show alllocks'
> > output confirms. But if we are holding this lock exclusively we shouldn't be
> > that deep in create code path, because we need hold this lock as reader.
> > It isn't visible in 'show alllocks' output, because this lock is special
> > (rrwlock.c).
> BTW, it seems that our 'stock' rwlock implements exactly the same thing as
> rrwlock.c - recursive readers, etc.
But you cannot sleep while holding our rwlock(9).
Pawel Jakub Dawidek http://www.wheelsystems.com
pjd at FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100310/22eec892/attachment.pgp
More information about the freebsd-stable