Edward Saipetch wrote: > Neal Pollack wrote: >> Ed Saipetch wrote: >>> Hello, >>> >>> I'm experiencing major checksum errors when using a syba silicon >>> image 3114 based pci sata controller w/ nonraid firmware. I've >>> tested by copying data via sftp and smb. With everything I've >>> swapped out, I can't fathom this being a hardware problem. >> >> I can. But I suppose it could also be in some unknown way a driver >> issue. >> Even before ZFS, I've had numerous situations where various si3112 >> and 3114 chips >> would corrupt data on UFS and PCFS, with very simple copy and checksum >> test scripts, doing large bulk transfers. >> >> Si chips are best used to clean coffee grinders. Go buy a real SATA >> controller. >> >> Neal > I have no problem ponying up money for a better SATA controller. I > saw a bunch of blog posts that people were successful using the card > so I thought maybe I had a bad card with corrupt firmware nvram. Is > it worth trying to trace down the bug?
Of course it is. File a bug so someone on the SATA team can study it. > If this type of corruption exists, nobody should be using this card. > As a side note, what SATA cards are people having luck with? A lot of people are happy with the 8 port PCI SATA card made by SuperMicro that has the Marvell chip on it. Don't buy other marvell cards on ebay, because Marvell dumped a ton of cards that ended up with an earlier rev of the silicon that can corrupt data. But all the cards made by SuperMicro and sold by them have the c rev or later silicon and work great. That said, I wish someone would investigate the Silicon Image issues, but there are only so many engineers, with so little time. >> >>> There have been quite a few blog posts out there with people having >>> a similar config and not having any problems. >>> >>> Here's what I've done so far: >>> 1. Changed solaris releases from S10 U3 to NV 75a >>> 2. Switched out motherboards and cpus from AMD sempron to a Celeron D >>> 3. Switched out memory to use completely different dimms >>> 4. Switched out sata drives (2-3 250gb hitachi's and seagates in >>> RAIDZ, 3x400GB seagates RAIDZ and 1x250GB hitachi with no raid) >>> >>> Here's output of a scrub and the status (ignore the date and time, I >>> haven't reset it on this new motherboard) and please point me in the >>> right direction if I'm barking up the wrong tree. >>> >>> # zpool scrub tank >>> # zpool status >>> pool: tank >>> state: ONLINE >>> status: One or more devices has experienced an error resulting in data >>> corruption. Applications may be affected. >>> action: Restore the file in question if possible. Otherwise restore >>> the >>> entire pool from backup. >>> see: http://www.sun.com/msg/ZFS-8000-8A >>> scrub: scrub completed with 140 errors on Sat Sep 15 02:07:35 2007 >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> tank ONLINE 0 0 293 >>> c0d1 ONLINE 0 0 293 >>> >>> errors: 140 data errors, use '-v' for a list >>> >>> >>> This message posted from opensolaris.org >>> _______________________________________________ >>> zfs-discuss mailing list >>> zfs-discuss@opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >>> >> > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
