Date: Thu, 5 Jul 2001 18:30:07 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Mark Valentine <mark@thuvia.demon.co.uk> Cc: Ben Smithurst <ben@FreeBSD.ORG>, "Antoine Beaupre (LMC)" <Antoine.Beaupre@ericsson.ca>, "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>, freebsd-current@FreeBSD.ORG Subject: Re: diskcheckd goes nuts on /dev/cd0 Message-ID: <Pine.BSF.4.21.0107051825100.55050-100000@besplex.bde.org> In-Reply-To: <200107042057.f64Kvc379721@dotar-sojat.thuvia.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <IBM-DTLA-307075> [148945/16/63] at ata0-master UDMA33 > da0: <IBM DMVS18V 0250> Fixed Direct Access SCSI-3 device > da1: <IBM DMVS18V 0250> Fixed Direct Access SCSI-3 device > cd1: <PLEXTOR CD-R PX-W124TS 1.02> Removable CD-ROM SCSI-2 device > cd0: <PLEXTOR CD-ROM PX-40TS 1.12> Removable CD-ROM SCSI-2 device > da2: <iomega jaz 1GB H.72> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0107051825100.55050-100000>