From owner-freebsd-questions Thu Feb 13 7:56:56 2003 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 5FA9B37B401 for ; Thu, 13 Feb 2003 07:56:55 -0800 (PST) Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CF1243F93 for ; Thu, 13 Feb 2003 07:56:54 -0800 (PST) (envelope-from msmith@code-fu.com) Received: from code-fu.com (pcp711718pcs.alxndr01.va.comcast.net [68.50.73.228]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.09 (built Jan 7 2003)) with ESMTP id <0HA900AUG89D6B@mtaout01.icomcast.net> for freebsd-questions@FreeBSD.ORG; Thu, 13 Feb 2003 10:56:02 -0500 (EST) Date: Thu, 13 Feb 2003 10:56:00 -0500 From: "Michael A. Smith" Subject: /usr filesystem crashing To: freebsd-questions@FreeBSD.ORG Message-id: <3E4BC010.6070609@code-fu.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030202 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm running FreeBSD 4.7-RC on an Athlon system that serves as our office fileserver (it has a Promise IDE RAID card and two mirrored 1-month old 40GB drives). I'm having some filesystem problems that fsck doesn't seem to fix. There is something going wrong with /dev/ar0s1g (my /usr slice). If left alone, with little activity, the machine seems to do OK. I can cause it to crash at any time, however, but doing something like running cvsup or trying to upgrade a big port. It crashes and dumps me into single-user mode to "run fsck manually." I've been running fsck repeatedly. Each time I run it, it finds problems with the /dev/ar0s1g slice. I can answer "Yes" to the recovery questions (or "No" for that matter) and reboot, but I can always crash the system again. I can even run fsck serveral times in a row and it reports problems (different inode numbers) each time. There are a few other problems the system is having (SSH, cups, and nmbd), but I suspect they're related to this disk issue. I've tried updating to 4.7-STABLE, but the filesystem locks up before I can get through it. Any thoughts (besides re-formatting, which I may do next week)? Thanks! -- Michael A. Smith Programmer at Large To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message