Date: Fri, 06 Jul 2001 15:25:26 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc diskcheckd.conf Message-ID: <20010706152526.C506@gsmx07.alcatel.com.au> In-Reply-To: <12032.994393836@critter>; from phk@critter.freebsd.dk on Fri, Jul 06, 2001 at 06:30:36AM %2B0200 References: <20010705215324.448BA3809@overcee.netplex.com.au> <12032.994393836@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2001-Jul-06 06:30:36 +0200, Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: >diskcheckd is not designed or intended to do scrubbing, its goal has >been reached if it does detection. The only problem is that soft errors won't be detected until they become hard errors - which is too late for the data on the disk. diskcheckd seems to be a slow (non I/O intensive) way to run "dd if=/dev/foo of=/dev/null bs=64k". It would be useful if the disk drivers could report soft errors so that something like diskcheckd could detect that a disk was going bad whilst it was still readable. Peter 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?20010706152526.C506>