From owner-freebsd-questions@FreeBSD.ORG Wed Jan 26 17:23:09 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 480E516A4CE for ; Wed, 26 Jan 2005 17:23:09 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 901FC43D1F for ; Wed, 26 Jan 2005 17:23:08 +0000 (GMT) (envelope-from freebsd-questions@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Ctqsl-0008Ob-00 for ; Wed, 26 Jan 2005 18:23:07 +0100 Received: from 65.213.7.6 ([65.213.7.6]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Jan 2005 18:23:07 +0100 Received: from scott by 65.213.7.6 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Jan 2005 18:23:07 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: "Scott I. Remick" Date: Wed, 26 Jan 2005 12:22:50 -0500 Lines: 17 Message-ID: <4w6ezec6ef4n$.oifwhsoezlhz.dlg@40tude.net> References: <200501261250.j0QCo2tT041759@uplift.hosp.misyshealthcare.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 65.213.7.6 User-Agent: 40tude_Dialog/2.0.14.1 X-Archive: encrypt Sender: news Subject: Re: FreeBSD 5.3 file system troubles X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: scott@sremick.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 17:23:09 -0000 On Wed, 26 Jan 2005 05:50:02 -0700 (MST), Terry R. Friedrichsen wrote: > Is anybody besides *me* having file system corruption problems with FreeBSD > 5.3? I've looked around on several of the mailing lists and found no men- > tion of this. Not the same problem as you, but I've been getting frequent ffs panics with 5.3 that I never got with 5.2.1. I didn't know the actual error at first because I'm in X most of the time and they wouldn't appear there (system would simply lock up). It wasn't until I started trying to update some ports from console only that I caught the error. It only seems to happen during periods of intense disk activity (writes?). I have the actual error written down at home. It always causes an fsck mess upon starting up again, which makes me nervous. There's certain tasks I simply cannot do anymore because they're write-intensive and I know they'll trigger the panic.