Re: kern/46053: Diagnostic assertion failed in uvm/uvm_vnode.c

[Hauke Fath <hf%spg.tu-darmstadt.de@localhost>]

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

From: Hauke Fath <hf%spg.tu-darmstadt.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
        David Holland <dholland-bugs%NetBSD.org@localhost>
Subject: Re: kern/46053: Diagnostic assertion failed in uvm/uvm_vnode.c
Date: Fri, 23 Mar 2012 10:23:41 +0100

 At 16:55 Uhr +0000 18.03.2012, David Holland wrote:
 > If
 > you're getting repeated fs corruption, fscking once in a while before
 > it becomes lethal may both keep the system running and help to track
 > down what's wrong.
 
 The file system in question was freshly restored from a dump. While that
 does not make fs corruption impossible, the fact that reducing blocksize of
 the fs in question from 64K to 32K made the panic go away (until recently,
 see my other mail) would speak against it.
 
        hauke
 
 --