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

From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org
Subject: Re: kern/30334: NetBSD/xen 3.0_BETA crashing with "error 5 while accessing filesystem"
Date: Wed, 25 May 2005 19:33:13 +0200

 On Wed, May 25, 2005 at 04:24:00PM +0000, evaldo@gardenali.biz wrote:
 > >Number:         30334
 > >Category:       kern
 > >Synopsis:       NetBSD/xen 3.0_BETA crashing with "error 5 while accessing filesystem"
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       medium
 > >Responsible:    kern-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Wed May 25 16:24:00 +0000 2005
 > >Originator:     Evaldo Gardenali
 > >Release:        3.0_BETA (20050523)
 > >Organization:
 > >Environment:
 > NetBSD flanders 3.0_BETA NetBSD 3.0_BETA (XENU) #0: Mon May 23 19:10:30 EDT 2005  evaldo@ezxen:/home/evaldo/src/sys/arch/i386/compile/obj/XENU i386
 > 
 > domain 0:
 > Linux ezxen 2.6.11.10-xen0 #2 Mon May 23 18:20:50 EDT 2005 i686 Intel(R) Xeon(TM) CPU 2.40GHz GenuineIntel GNU/Linux
 > 
 > >Description:
 > The machine runs okay for some time, then crashes all out of the blue, normally when it is idle... this last time, it was up for 12 hours when this happened.
 > 
 > unable to get a core dump because there is no dump partition.
 > 
 > relevant Xen configuration:
 > kernel = "/live/evaldo/netbsd-XENU"
 > memory = 256
 > cpu = -1   # leave to Xen to pick
 > vif  = [ 'mac=ba:be:ba:be:ba:be,bridge=xen-br2' ]
 > disk = [ 'file:/live/evaldo/netbsd.root,hda1,w' ]
 > root = "/dev/wd0d"
 > autorestart = True
 > 
 > /etc/fstab contents:
 > /dev/xbd0a / ffs rw,softdep 1 1
 > /dev/cgd0a /usr ffs rw,softdep 1 2
 > /dev/cgd1b none swap sw 0 0
 > kernfs /kern kernfs rw
 > procfs /proc procfs rw,noauto
 > 
 > 
 > 
 > standard netbsd-XENU kernel, cross-built from linux in a 'build.sh -N 1 -m i386 release'
 > 
 > debugger output:
 > cgd0: error 5
 
 error 5 is "I/O error". It could be anything, including a real I/O error 
 reported by the xbd backend in domain0. Did you look at the linux kernel
 messages ?
 
 > /: got error 5 while accessing filesystem
 > panic: softdep_deallocate_dependencies: unrecovered I/O error
 
 Yes, softdep deals very badly with device errors :(
 
 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --