From owner-freebsd-questions Tue Nov 18 10:57:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13276 for questions-outgoing; Tue, 18 Nov 1997 10:57:46 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from luke.cpl.net (luke.cpl.net [207.67.172.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13268 for ; Tue, 18 Nov 1997 10:57:43 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.8/8.6.12) with SMTP id KAA01237; Tue, 18 Nov 1997 10:56:28 -0800 (PST) Date: Tue, 18 Nov 1997 10:56:27 -0800 (PST) From: Shawn Ramsey To: Doug White cc: questions@FreeBSD.ORG Subject: Re: fsck In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Why is it when I run fsck on /dev/wd1se I get a (NO WRITE) (Mounted on > > /disk2). If I do fsck /dev/wd0a which is mounted /, and doesnt do that. > > Just wondering, because I also admin a BSDI news server. The news spool > > kept failing filesystem checks, and would crash within minutes. If I could > > have fsck'd the filesystem, I probably could have avoided newfs'ing it... > > You should fsck volumes before mounting them. fsck can't fix broken fs's > while they're mounted as it would probably cause a kernel panic if someone > tried to open a file while you were working on it. Hmm, why didnt I think of that? DOh! Oh well, the news spool could use a clean start once in a while...