From owner-freebsd-current Thu Jul 5 1:32:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E9BFE37B407; Thu, 5 Jul 2001 01:32:17 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA32460; Thu, 5 Jul 2001 18:32:09 +1000 Date: Thu, 5 Jul 2001 18:30:07 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Mark Valentine Cc: Ben Smithurst , "Antoine Beaupre (LMC)" , "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Subject: Re: diskcheckd goes nuts on /dev/cd0 In-Reply-To: <200107042057.f64Kvc379721@dotar-sojat.thuvia.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 4 Jul 2001, Mark Valentine wrote: > > From: ben@freebsd.org (Ben Smithurst) > > I think excluding CDs and MDs should solve most of the problems that > > have been reported, I'm not sure what the situation with zip/jaz type > > things is though. Are they included in kern.disks? Anyone? > > kern.disks: md0 da2 da1 da0 cd1 cd0 ad0 > > ad0: 73308MB [148945/16/63] at ata0-master UDMA33 > da0: Fixed Direct Access SCSI-3 device > da1: Fixed Direct Access SCSI-3 device > cd1: Removable CD-ROM SCSI-2 device > cd0: Removable CD-ROM SCSI-2 device > da2: Removable Direct Access SCSI-2 device > > da2 should not be checked. ad0 is okay, it's not a flash device... > > It's still unsafe to clean ad* or da* in the default disckcheckd.conf. kern.disks: afd0 ad4 ad0 afd0 is a zip. I think afd can have actual floppies in it. I think diskcheckd.conf should check no disks by default. Checking is bad for many types of disks. It's bad for all disks on laptops running off batteries. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message