From owner-freebsd-current Wed Jul 4 0: 0:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 50C0E37B407 for ; Wed, 4 Jul 2001 00:00:05 -0700 (PDT) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f64705m08269 for freebsd-current@freebsd.org; Wed, 4 Jul 2001 00:00:05 -0700 (PDT) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <200107040700.f64705m08269@troutmask.apl.washington.edu> Subject: diskcheckd goes nuts on /dev/cd0 To: freebsd-current@freebsd.org Date: Wed, 4 Jul 2001 00:00:05 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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 I'm sure this is pilot error, but ... I updated a pre june 13th current to a july 3 current. Ran mergemaster and installed /etc/diskcheckd.conf without modification. Upon reboot I saw 1000s of the following message streaming up the console: dscheck(cd0): bio_bcount 512 is not on a sector boundary (ssize 2048) Checking /var/log/messages I find (note date and machine name removed): diskcheckd[213]: /dev/cd0 has 2048 byte sectors, may cause minor problems /boot/kernel/kernel: dscheck(cd0): bio_bcount 512 is not on a sector boun dary (ssize 2048) last message repeated 3 times diskcheckd[213]: error reading 512 bytes from sector 0 on /dev/cd0 Variations on the above 5 line fill that last 700 lines of /var/log/messages. I checked src/UPDATING for a diskcheckd HEADS_UP. Nada. Read the diskcheckd and the diskcheckd.conf man pages. So, I'll "fix" the problem. 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. 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. -- Steve http://troutmask.apl.washington.edu/~kargl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message