From owner-freebsd-stable Mon Aug 14 21: 0:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 0993D37B8F5 for ; Mon, 14 Aug 2000 21:00:26 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 67BA91C41; Tue, 15 Aug 2000 00:00:25 -0400 (EDT) Date: Tue, 15 Aug 2000 00:00:25 -0400 From: Bill Fumerola To: "Tyson N. Trebesch" Cc: freebsd-stable@freebsd.org Subject: Re: A note about fsck Message-ID: <20000815000025.S65562@jade.chc-chimes.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from trebesch@mcn.net on Mon, Aug 14, 2000 at 09:48:55PM -0600 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 14, 2000 at 09:48:55PM -0600, Tyson N. Trebesch wrote: > > In general, it is a good idea to use fsck on the raw device and not the > block device when you're interested in fixing the filesystem. That is, > > fsck /dev/rad0s1a > > is probably better than > > fsck /dev/ad0s1a > > given inconsistencies that arise between the block device and the buffer > cache. What is a block device? -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org PS. Yes, yes I know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message