Re: kern/42551: Lockdebug assert in wapbl when running zpool

[ober%linbsd.org@localhost]

The following reply was made to PR kern/42551; it has been noted by GNATS.

From: ober%linbsd.org@localhost
To: gnats-bugs%NetBSD.org@localhost, David Holland 
<dholland-bugs%netbsd.org@localhost>
Cc: 
Subject: Re: kern/42551: Lockdebug assert in wapbl when running zpool
Date: Wed, 06 Jan 2010 21:19:39 -0500

 > The following reply was made to PR kern/42551; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: kern/42551: Lockdebug assert in wapbl when running zpool
 > Date: Thu, 31 Dec 2009 17:17:25 +0000
 > 
 >  On Thu, Dec 31, 2009 at 09:10:00AM +0000, ober%netbsd.org@localhost wrote:
 >   > LOCKDEBUG/DIAGNOSTIC/DEBUG enabled GENERIC AMD64 from today
 >   > panics on command "zpool create pancake /dev/sd1a"
 >   > with
 >   > panic: kernel diagnostic assertion "rw_lock_held(&wl->wl_rwlock)" failed:
 >  file "/usr/src/sys/kern/vfs_wapbl.c", line 1542
 >   > __kernassert() at netbsd:__kernassert+0x2d
 >   > wapbl_add_buf() at netbsd:wapbl_add_buf+0x36
 >   > bdwrite() at netbsd:bdwrite+0xc2
 >   > ffs_update() at netbsd:ffs_update+0x1ce
 >   > ffs_full_fsync() at netbsd:ffs_full_fsync+0x38b
 >   > ffs_fsync() at netbsd:ffs_fsync+0x4b
 >   > VOP_FSYNC() at netbsd:VOP_FSYNC+0x70
 >   > vinvalbuf() at netbsd:vinvalbuf+0xee
 >   > spec_close() at netbsd:spec_close+0x82
 >  
 >  Just to confirm: your /dev is on a WAPBL volume? Or are we once again
 >  calling WAPBL ops on non-WAPBL fses?
 >  
 >  -- 
 >  David A. Holland
 >  dholland%netbsd.org@localhost
 >  
 Hello David,
       Yes / is on wapbl.