Date: Sun, 14 May 1995 09:25:18 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: hackers@FreeBSD.org Cc: rgrimes@gndrsh.aac.dev.com Subject: "bad144" for SCSI Message-ID: <199505141325.JAA17288@hda.com>
next in thread | raw e-mail | index | archive | help
Rodney W. Grimes writes: (redirecting to -hackers) (...) > There is no bad144 support in the scsi disk drivers, so this will > not work for mapping blocks out of a scsi disk using bad144, but > you can use scsi(8) to turn on automatic read reallocation and then > scan the disk with this and it should automagically remap the > block for you!! Unless you can't read the block, since the drive will only map out blocks when it can successfully read the data in the block. You could "scrub" the disk by reading/ignoring errors/writing the disk, though you'll lose the data in any block you can't read. I have a utility that takes a drive and a list of blocks and forceably map out those blocks. The best utility is probably a scrub that takes a range of blocks and tries to read/write them. If it can't read the block, it will finally turn off error checking, read whatever it can, and write it back to the (automatically slipped on write) block. Obviously this corrupts the block, though it is the best you can do in this situation. I can merge one of these into scsi(8) after the code freeze lifts. I don't know if people mind that I keep clogging up scsi(8) with more stuff, but I can't see having lots of little SCSI utilities, especially since these kind of utilities should be in /sbin. Joerg proposed adding a kind of script capability to scsi(8) to do this. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505141325.JAA17288>