NetBSD doesn seem to like my SCSI disk. Is there any way I can prevent this annoying filesystem damage?
This problem results from a recognized but as yet unfixed bug in the ncrscsi driver. For some reason, it seems to attack Quantum drives more often than others. The usual symptoms are that under heavy disk usage, the drive light suddenly stays on, but the system is hung. After rebooting, an fsck run will turn up rather nasty filesystem damage. Sometimes you may not notice the damage until you try to run some binary file and realize that it is now a device file instead (i.e. its directory listing looks something like b——— or c———). In order to fix the problem, Scott Reynolds (scottr@og.org) wrote the sbc scsi driver to replace the standard ncrscsi driver. Since this driver operates in polled mode by default, it is a little slower and more CPU-intensive than the stock ncrscsi driver (especially on slow SCSI devices like CD-ROM’s and tape drives). However, it is much less likely to corrupt your data. Scott recommends that you use it instead only if you are currently having trou
Related Questions
- How do you create a RAID array using IDE/Ultra DMA disk drives and why does an IDE/Ultra DMA RAID controller use a SCSI interface?
- When installing Windows NT 4.0 to a SCSI disk, the host adapter is seen but the attached disks are not. Whats Wrong?
- NetBSD doesn seem to like my SCSI disk. Is there any way I can prevent this annoying filesystem damage?
