Date: Thu, 10 Oct 2002 10:32:23 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Jack Twilley <jmt@twilley.org> Cc: freebsd-questions@freebsd.org Subject: Re: Corrupt data with vinum in 4.6.2-RELEASE Message-ID: <20021010010223.GA87617@wantadilla.lemis.com> In-Reply-To: <86d6qjw2gw.fsf@duchess.twilley.org> References: <86lm58w796.fsf@duchess.twilley.org> <20021010003305.GN1415@wantadilla.lemis.com> <86d6qjw2gw.fsf@duchess.twilley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 9 October 2002 at 17:40:31 -0700, Jack Twilley wrote: >>>>>> "Greg" == Greg Lehey <Greg> writes: > >>> I had a bad experience this weekend with vinum, SCSI and new >>> disks, and I'm not sure which part's at fault. > >> Well, you're getting mulitple error messages from the SCSI >> 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? No, Vinum only finds out about errors the SCSI subsystem chooses to report. As regards the corruption, we haven't seen any details > I don't know, which is one of the reasons I asked here. Sure. >>> I installed ten new 4G disks, built two striped plexes of five >>> disks each, and mirrored them. Two drives on the second plex >>> generated pages of SCSI errors on the console when I was >>> populating the new volume from my backups. Many of the files >>> were corrupted in the restore. The vinum statistics reported no >>> errors for the drive. I stopped the second plex, rebooted, and >>> did another restore. The restore went flawlessly. I started >>> the second plex, and the same two drives generated pages of SCSI >>> errors on the console. Still no errors reported by vinum. The >>> files were corrupted. What's going on here? > >> I don't know. All I see is SCSI errors. That shouldn't cause >> corruption, but then neither should Vinum. I'd suggest you >> attend to the SCSI problems and see if the others go away; I'd >> expect them to. If you want to follow the Vinum aspect, see the >> 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. Sorry, I've never seen this kind of problem before. It would be good if you could supply some details of your hardware. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021010010223.GA87617>