Date: Sun, 24 Mar 1996 22:06:41 +0100 (MET) From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: FreeBSD 2.1.0 System Crashes often, please help. (fwd) Message-ID: <199603242106.WAA05587@uriah.heep.sax.de>
next in thread | raw e-mail | index | archive | help
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 <brian@awfulhak.demon.co.uk> Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603242106.WAA05587>