Date: Sun, 16 Nov 2003 13:06:11 -0500 From: Mike Tancsa <mike@sentex.net> To: "Douglas K. Rand" <rand@meridian-enviro.com> Cc: freebsd-hardware@freebsd.org Subject: Re: asr monitoring Message-ID: <f3efrvotqh1trgct2kfn3k29mosohsgvfl@4ax.com> In-Reply-To: <874qx5x8yz.wl@delta.meridian-enviro.com> References: <8765hlxkyd.wl@delta.meridian-enviro.com> <200311160207.hAG27cV64876@agena.meridian-enviro.com> <874qx5x8yz.wl@delta.meridian-enviro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is really odd. We have quite a few cards deployed on FreeBSD and have none of these problems. Which 3ware cards are you using ? What is the firmware rev ? ---Mike On Sat, 15 Nov 2003 21:56:04 -0600, in sentex.lists.freebsd.hardware you wrote: >Simon> Please do share your unhappy experience with 3ware. > >We've had one troublesome system, running supported IBM disks (120 GB >IC35L120AVVA07 disks) where we have repeated drive timeout errors, and >recently the mirror sets (we're running 4 disks in a RAID-10) get out >of sync. I had it once where the system was still stable (kind of at >least) and an MD5 checksum of a large file would come up different, >but always one of two values. I did the "verify array" operation at >the BIOS, and it found "an unknown error". (If its unknow, how can it >be an error?) This causes the volume to be initialized, and then my >MD5 checksum is always the same. > >We just had one of our MySQL servers die with a corrupted page in the >database, ran the verify array on that system, and again we got the >unknown error. (This system also has supported disks, the IBM 80 GB >IC35L080AVVA07.) > >I'm really getting worried now with the mirror sets getting out of >sync, this is not a good thing at all.=20 > >The rumor mill has 3ware supporting FreeBSD directly with their 7.7 >release of drivers, so I'll probably try that when it happens.=20 > >simon> 3ware can email you if something goes wrong, no need to watch >simon> syslog. > >Right, I guess I just like the syslog approach, it works even if 3dmd >isn't working, or the system is so borked it can't send email, in >which case it probably can't send a syslog message either. :( >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to = "freebsd-hardware-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3efrvotqh1trgct2kfn3k29mosohsgvfl>