From owner-freebsd-current Sun Mar 24 14:24:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28049 for current-outgoing; Sun, 24 Mar 1996 14:24:17 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA28029 for ; Sun, 24 Mar 1996 14:24:04 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA03582 for ; Mon, 25 Mar 1996 00:23:54 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA01019 for freebsd-current@freebsd.org; Sun, 24 Mar 1996 23:23:53 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id WAA05587; Sun, 24 Mar 1996 22:06:41 +0100 (MET) Date: Sun, 24 Mar 1996 22:06:41 +0100 (MET) Message-Id: <199603242106.WAA05587@uriah.heep.sax.de> X-Newsreader: knews 0.9.3 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: FreeBSD 2.1.0 System Crashes often, please help. (fwd) To: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does this give a hint to anybody? ----- Forwarded Message ----- From: brian@awfulhak.demon.co.uk (Brian Somers) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD 2.1.0 System Crashes often, please help. Date: 19 Mar 1996 17:44:25 -0000 Organization: Coverform Ltd. Message-ID: <4imrpp$kg@anorak.coverform.lan> [Story about crashes deleted] I installed FreeBSD-2.1.0 as an upgrade to 2.0.5 - 2.0.5 had crashed about 0 - 1 times (barring a ppp kernel problem that was patched shortly after the 2.0.5 release) in the ~6 months I had it installed. 2.1.0 crashed _EVERY_ night. Eventually, I found that I had a /var/cron/tabs/root file in place that looked almost exactly the same as the /etc/crontab file that was installed by the upgrade. /etc/daily was the culprit. Because it was being run twice at exactly the same time, the system crashed. As I remember, it was a vnode inconsistency problem - similar to the problem mentioned previously in this thread with the simultaneous dumps....... It sounds like one of the driver routines is leaving a vnode in a temporarily inconsistent state ? Does this shine any light ? It's as bright as my tourch goes ! -- Brian Don't _EVER_ lose your sense of humour....