Thanks for the info on the yukon driver. I realize too many variables makes things impossible to determine, but I had made these hardware changes awhile back, and they seemed to work fine at the time. Since they aren't now, even in the older OpenSolaris (i've tried 2009.06 and 2008.11 now), the problem seems to be a hardware quirk, and the only way to narrow that down is to change hardware back until it works like it used to in at least the older snv builds. I've ruled out the ethernet controller. I'm leaning toward the current motherboard (Asus P5W64) not playing nicely with the LSI cards, but it will probably be several days until I get to the bottom of this since it takes awhile to test after making a change...
Thanks, Chad On Mon, Dec 07, 2009 at 11:09:39AM +1000, James C. McPherson wrote: > > > Gday Chad, > the more swaptronics you partake in, the more difficult it > is going to be for us (collectively) to figure out what is > going wrong on your system. Btw, since you're running a build > past 124, you can use the "yge" driver instead of the yukonx > (from Marvell) or myk (from Murayama-san) drivers. > > As another comment in this thread has mentioned, a full scrub > can be a serious test of your hardware depending on how much > data you've got to walk over. If you can keep the hardware > variables to a minimum then clarity will be more achievable. > > > thankyou, > James C. McPherson > -- > Senior Kernel Software Engineer, Solaris > Sun Microsystems > http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
