Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2811 comp.os.386bsd.questions:15610 Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!scsing.switch.ch!news.belwue.de!delos.stgt.sub.org!nadia.s.bawue.de!luva!migieger From: migieger@luva.lb.bawue.de (Michael Giegerich) Subject: Re: Help! File system damaged after normal reboot! Organization: private FreeBSD site Message-ID: <D1wCMG.2ru@luva.lb.bawue.de> References: <D1uD3I.Ep@store.elvisti.kiev.ua> Date: Wed, 4 Jan 1995 19:54:15 GMT Lines: 20 In article <D1uD3I.Ep@store.elvisti.kiev.ua>, Andrew V. Stesin <stesin@elvisti.kiev.ua> wrote: >Greetings, > >my FreeBSD-1.1.5 started suddenly to show an unusual and annoying >behavior when booting up after a normal `halt` or `reboot`. >The machine -- 486dx50 with VESA IDE, manufactured by SOYO(tm) >and 2 Conner 420Mb disks -- randomly suffers a trouble. > >fsck tells that there are "unexpected inconsistencies", >"DUP/BAD" and shows some inode No. Last time it happened, fsck >tried to remove libc.a!!! I experienced the same error messages from fsck. After upgrading to 2.0 all went normal again. I believe the vm system was the culprit in 1.1.5.x (or some patch added to the system?). -- Michael Giegerich migieger@luva.lb.bawue.de