From owner-freebsd-hackers Sun Jun 13 2: 6:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id E4B2414CC7 for ; Sun, 13 Jun 1999 02:06:26 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 58927 invoked from network); 13 Jun 1999 09:06:25 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 13 Jun 1999 09:06:25 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id EAA53015; Sun, 13 Jun 1999 04:06:25 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Sun, 13 Jun 1999 04:06:25 -0500 (CDT) From: David Scheidt To: Bernd Walter Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates problem? In-Reply-To: <19990613084249.A66895@cicely8.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Jun 1999, Bernd Walter wrote: > On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote: > > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying > > to load the oss driver, which is not too shocking. What was shocking > > was the damage done to my filesystem. The automatic fsck failed, > > with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED > > INODE I=39684. > > > What kernel-config are you using? > I have had several fs-crashes because of a to high configured maxusers. The only diffs between my config file and GENERIC are: 1. softupdates 2. no support for hardware I haven't got 3. pty is 64 I am not actually complaining about the panic; I think the oss driver is a piece of crap. I just happened to have a soundcard that they support that the FreeBSD drivers don't, and a .wav file I wanted to listen to. What does disturb me is the damage done to a pretty quiet filesystem. I wouldn't have thought that toasting a whole bunch of files that were not in use would be the normal behavior. I have seen lots of panics, but have never seen filesystem damage as bad as this. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message