From owner-freebsd-questions Thu Jan 12 09:42:17 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA26282 for questions-outgoing; Thu, 12 Jan 1995 09:42:17 -0800 Received: from moon.pr.erau.edu (moon.pr.erau.edu [192.101.135.8]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA26276 for ; Thu, 12 Jan 1995 09:42:14 -0800 Received: by moon.pr.erau.edu (Smail3.1.29.1 #15) id m0rSTUg-00047MC; Thu, 12 Jan 95 10:39 MST Date: Thu, 12 Jan 1995 10:39:30 -0700 (MST) From: Stephen Waits To: "Jordan K. Hubbard" cc: questions@FreeBSD.org Subject: Re: news server filesystems.. In-Reply-To: <13334.789749966@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@FreeBSD.org Precedence: bulk On Tue, 10 Jan 1995, Jordan K. Hubbard wrote: > > Our news server filesystem needs almost nightly fsck's in order to stay > > up. Is there anything I can do to avoid this? I assume there isn't - > > news servers are just hard on filesystems... (???) > > BLECH?? This is not right. Can you please elaborate on `in order to > stay up.'? What happens if you don't bring them down and fsck them > nightly? You should be able to go for weeks, if not months, without > having to fsck anything.. If I don't nightly fsck (usually -y) my news spool partition there is almost always some sort of bad directory (that my news server can't write into) or file that makes my news server unhappy. fsck -y usually clears out a _LOT_ of problems. It is 1.1.5.1 (waiting for 2.x to settle down) with an Ultrastor 34F (VLB) and a connor 1.3 G SCSI-2 drive. Any Ideas? --Steve