From owner-freebsd-questions  Tue Nov 18 01:16:35 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA06281
          for questions-outgoing; Tue, 18 Nov 1997 01:16:35 -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 BAA06268
          for <questions@freebsd.org>; Tue, 18 Nov 1997 01:16:22 -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 BAA00374 for <questions@freebsd.org>; Tue, 18 Nov 1997 01:03:17 -0800 (PST)
Date: Tue, 18 Nov 1997 01:03:01 -0800 (PST)
From: Shawn Ramsey <shawn@luke.cpl.net>
To: questions@freebsd.org
Subject: fsck
Message-ID: <Pine.BSF.3.95.971118005926.357A-100000@luke.cpl.net>
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...

(The example above about (NO WRITE), etc is on a FreeBSD-2.2.5-stable
system)