From owner-freebsd-hardware Tue Jun 16 22:32:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11088 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 22:32:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bubble.didi.com (nor-la4-23.ix.netcom.com [204.31.237.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11077 for ; Tue, 16 Jun 1998 22:32:37 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.8.8/8.8.8) id AAA07780; Wed, 17 Jun 1998 00:32:19 -0500 (CDT) (envelope-from asami) Date: Wed, 17 Jun 1998 00:32:19 -0500 (CDT) Message-Id: <199806170532.AAA07780@bubble.didi.com> To: richard@pegasus.com CC: sef@kithrup.com, hardware@FreeBSD.ORG In-reply-to: <199806162020.KAA15243@pegasus.com> (richard@pegasus.com) Subject: Re: scsi disk question From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * The drive knows nothing of filesystem file creation and deletion. You * need to reformat the disk. The latter doesn't follow from the former. :) * By deleting the file you've put the bad block back into play. It will * probably surface elsewhere. Yes, but when the block is allocated again to a file, it will first being written to, at which time the drive will reallocate it. The reason why it initially gave you errors was because the disk cannot pretend nothing bad happened when you have read errors. It can do that for write errors (assuming you haven't run out of spare blocks). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message