From owner-freebsd-current Wed Jul 4 1:17:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id 3B84537B405 for ; Wed, 4 Jul 2001 01:17:42 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f648J3A73072; Wed, 4 Jul 2001 09:19:03 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.4/8.11.4) id f648IBE51086; Wed, 4 Jul 2001 09:18:11 +0100 (BST) (envelope-from mark) Date: Wed, 4 Jul 2001 09:18:11 +0100 (BST) From: Mark Valentine Message-Id: <200107040818.f648IBE51086@dotar-sojat.thuvia.org> In-Reply-To: "Steven G. Kargl"'s message of Jul 4, 7:11am X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: kargl@troutmask.apl.washington.edu ("Steven G. Kargl"), freebsd-current@freebsd.org Subject: Re: diskcheckd goes nuts on /dev/cd0 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 > From: kargl@troutmask.apl.washington.edu ("Steven G. Kargl") > Date: Wed 4 Jul, 2001 > Subject: diskcheckd goes nuts on /dev/cd0 > However, it seems that default > settings in diskcheckd.conf that tell diskcheckd to check > all kern.disks in system and setting diskcheckd_enable="YES" > in /etc/defaults/rc.conf without a HEAD-UPS is somewhat > alarming. Yes, I thought this too. Isn't this likely to do damage to some types of media, for example Jaz disks which like to spin down most of the time (and which aren't cheap)? Also, it's pointless checking md devices... What about stuff like flash RAM appearing as IDE disks? > As a side question, why is diskcheckd even looking at > at /dev/cd0? From reading the man pages, one would infer > that diskcheckd is intended to check for read errors on > /dev/daYADA and /dev/adYADA and maybe /dev/fd0. Just using kern.disks by default seems unwise. Is there a way to determine which devices are fixed magnetic disks? (For SCSI? IDE? Other?) I'd suggest that until this is resolved that the default diskcheckd.conf not check anything; even just defaulting to ad0 probably isn't safe. Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message