From owner-freebsd-questions Tue Nov 18 09:58:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA09606 for questions-outgoing; Tue, 18 Nov 1997 09:58:29 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA09599 for ; Tue, 18 Nov 1997 09:58:24 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id JAA01468; Tue, 18 Nov 1997 09:58:22 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 18 Nov 1997 09:58:22 -0800 (PST) From: Doug White Reply-To: Doug White To: Shawn Ramsey 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 On Tue, 18 Nov 1997, Shawn Ramsey wrote: > 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. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major