>>>>> "Greg" == Greg Lehey <Greg> writes: Jack> I had a bad experience this weekend with vinum, SCSI and new Jack> disks, and I'm not sure which part's at fault.
Greg> Well, you're getting mulitple error messages from the SCSI Greg> subsystem, and none from Vinum. True. But is vinum supposed to detect the SCSI errors and do something about it, like protect my data from corruption? I don't know, which is one of the reasons I asked here. Jack> I installed ten new 4G disks, built two striped plexes of five Jack> disks each, and mirrored them. Two drives on the second plex Jack> generated pages of SCSI errors on the console when I was Jack> populating the new volume from my backups. Many of the files Jack> were corrupted in the restore. The vinum statistics reported no Jack> errors for the drive. I stopped the second plex, rebooted, and Jack> did another restore. The restore went flawlessly. I started Jack> the second plex, and the same two drives generated pages of SCSI Jack> errors on the console. Still no errors reported by vinum. The Jack> files were corrupted. What's going on here? Greg> I don't know. All I see is SCSI errors. That shouldn't cause Greg> corruption, but then neither should Vinum. I'd suggest you Greg> attend to the SCSI problems and see if the others go away; I'd Greg> expect them to. If you want to follow the Vinum aspect, see the Greg> man page for details of how to solve problems. Well, suggestions on how to attend to the SCSI problems would be appreciated. The hardware appears to pass self-tests. The cabling is run properly. My tape drive is on the same bus and my backups have passed multiple spot checks so I don't think it's a termination issue. If there's any extra debugging I can enable to test the card or anything like that, please let me know. I'm very interested in being able to sleep without nightmares of lost data. Jack. -- Jack Twilley jmt at twilley dot org http colon slash slash www dot twilley dot org slash tilde jmt slash
msg04581/pgp00000.pgp
Description: PGP signature
