Still on by default.
On Wed, 18 Jul 2001, Alfred Perlstein wrote:
> * Matthew Jacob <[EMAIL PROTECTED]> [010718 16:33] wrote:
> >
> > So, I took a SCSi disk away. Diskcheckd started complaining. However,
> > a camcontrol rescan couldn't make the disk go away until I killed off
> > diskcheckd, which then closed the disk, allowing the rescan to remove it.
> > Bad. Bad. Bad.
> >
> > ev/da4
> > Jul 18 14:31:15 diskcheckd[202]: error reading 512 bytes from sector 908502 on
> > /dev/da4
> > Jul 18 14:31:15 diskcheckd[202]: error reading 512 bytes from sector 908505 on
> > /dev/da4
> > Jul 18 14:31:15 diskcheckd[202]: error reading 512 bytes from sector 908506 on
> > /dev/da4
> > Jul 18 14:31:15 diskcheckd[202]: error reading 512 bytes from sector 908513 on
> > /dev/da4
> > Jul 18 14:31:51 diskcheckd[202]: error reading 512 bytes from sector 908629 on
> > /dev/da4
> > Jul 18 14:31:51 diskcheckd[202]: error reading 512 bytes from sector 908636 on
> > /dev/da4
> > (da4:isp3:0:5:0): Synchronize cache failed, status == 0x4a, scsi status == 0x0
> > (da4:isp3:0:5:0): removing device entry
>
> Is diskcheckd still on by default? If so, can whomever enabled it
> turn it off? If not I'll be 'fixing' this oversight this afternoon.
>
> thanks,
> --
> -Alfred Perlstein [[EMAIL PROTECTED]]
> Ok, who wrote this damn function called '??'?
> And why do my programs keep crashing in it?
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
