Re: kern/37955: Kernel Panic NetBSD 4.0 blkfree

[Vincent van den Berg <vincent%mijnpostvak.in@localhost>]

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

From: Vincent van den Berg <vincent%mijnpostvak.in@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/37955: Kernel Panic NetBSD 4.0 blkfree
Date: Mon, 11 Feb 2008 01:12:08 +0100

 David Holland schreef:
 > The following reply was made to PR kern/37955; it has been noted by GNATS.
 >
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 >      netbsd-bugs%netbsd.org@localhost
 > Subject: Re: kern/37955: Kernel Panic NetBSD 4.0 blkfree
 > Date: Sat, 9 Feb 2008 23:28:01 +0000
 >
 >  On Mon, Feb 04, 2008 at 04:45:02PM +0000, vlvdberg%mijnpostvak.in@localhost 
 > wrote:
 >   > Feb  4 01:59:52 chernobyl /netbsd: panic: blkfree: freeing free frag
 >  
 >  This is usually caused by working on a filesystem that hasn't been
 >  fsck'd. Have you tried fscking the volume? (Use -f to make it go ahead
 >  even if it thinks it's clean.)
 >  
 >  -- 
 >  David A. Holland
 >  dholland%netbsd.org@localhost
 >  
 >   
 Hello David,
 
 Yes I tried.. The filesystem is marked as clean. The problem still 
 persists, it is mainly occuring while the system is creating it's daily 
 backups to an external harddrive using rsnapshot (and thus rsync). 
 Yesterday the kernel panic'd while I was logged in with ssh and the 
 system began it's daily backup cycle... Ofcourse I was thrown off with a 
 locked (non-responsive) shell. I've never noticed this error while using 
 NetBSD 3.1, but
 I must confess I wasn't using rsnapshot by then. I've switched to the 
 netbsd-4-0-RELEASE branch, but the problem occurs there as well.
 
 Feb 11 00:26:04 chernobyl /netbsd: panic: blkfree: freeing free frag
 
 
 Regards,
 
 
 Vincent