Date: Fri, 6 Jul 2001 11:47:06 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Peter Wemm <peter@wemm.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc diskcheckd.conf Message-ID: <20010706114706.A41701@walton.maths.tcd.ie> In-Reply-To: <15614.994404185@critter>; from phk@critter.freebsd.dk on Fri, Jul 06, 2001 at 09:23:05AM %2B0200 References: <20010706070905.7BC4D3809@overcee.netplex.com.au> <15614.994404185@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 06, 2001 at 09:23:05AM +0200, Poul-Henning Kamp wrote: > Eitherway, I will argue that we need more real-world experience with > diskcheckd before we decide anything. My experience so far with diskcheckd is that is needs to be somewhat more clever or off by default. Of -current machines we have: - on one it tried to scan my SCSI zip disk, which wasn't ready. It also tried to scan some cd drives, but I think that's been fixed. - on another it's scanning a vmware disk, which isn't really that useful. - on another it started scanning a disk which we usually keep spun-down to stop it from getting too hot. I suspect it's also undesirable on laptops where you want to spin down disks or where da0 is actually the first floppy drive (would 64k every second or so max out a floppy drive?). Maybe there is some way it can avoid disks with removable media or spun down disks? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010706114706.A41701>