Re: kern/37955: Kernel Panic NetBSD 4.0 blkfree

[David Holland <dholland-bugs%netbsd.org@localhost>]

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

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: Vincent van den Berg <vincent%mijnpostvak.in@localhost>
Cc: gnats-bugs%netbsd.org@localhost, David Holland 
<dholland-bugs%netbsd.org@localhost>
Subject: Re: kern/37955: Kernel Panic NetBSD 4.0 blkfree
Date: Tue, 11 Mar 2008 02:18:58 +0000

 On Mon, Mar 10, 2008 at 01:31:52PM +0100, Vincent van den Berg wrote:
  > >Just to check, when you say clean, you mean like this, right?
  > >[snip]
  >
  > Hi David,
  > 
  > Yes, I forced fsck on all volumes. It goes through them like you 
  > described (Phases etc.) and it gives no errors.
 
 Sigh. It would have been much simpler if the problem turned to be just
 that the fs was corrupt. Or at least, simpler to make it work again.
 
 I'm wondering if this is the same as or related to kern/37590.
 
 Do you have enough disk space to make a copy of the contents of the fs
 in a file? If you do, do that, fsck it, then use vnd(4) to mount the
 file as a fs, and try running rsnapshot or rsync or whatnot. While
 that's useless for backing up, if it works reliably, then we can be
 pretty sure it's a usb issue and not a filesystem issue, which rules
 out lots and lots of code that might be causing problems. On the other
 hand, if it blows up that way too, then we can be pretty sure it's
 *not* a usb issue.
 
 Also, when sending mail, cc: gnats-bugs%netbsd.org@localhost; then it'll go 
into
 the PR database so other developers can see, which is a good thing
 anytime something mysterious is happening.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost