search for: si3124

A little back story: I have a Norco DS-1220, a 12 bay SATA box, it is connected to eSATA (SiI3124) via PCI-X two drives are straight connections, then the other two ports go to 5x multipliers within the box. My needs/hopes for this was using 12 500GB drives and ZFS make a very large & simple data dump spot on my network for other servers to rsync to daily & use zfs snapshots for

...0.0 0.0 0.0 0 0 c7t1d0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c7t2d0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c7t3d0 Perhaps related bugs: Disk access stops for minutes with 100% blocking http://bugs.opensolaris.org/view_bug.do?bug_id=6544624 si3124 driver loses interrupts. http://bugs.opensolaris.org/view_bug.do?bug_id=6566207 Any ideas? Should I ditch the SIL3224 cards as they seem to have a bad rep on this maillist? I have ordered a Sun SG-XPCI8SAS-E-Z which is an SAS PCI-X card but it will cost me a lot more money just without adding...

Perhaps a bit off-topic (I asked on the rescue list -- http://web.archiveorange.com/archive/v/OaDWVGdLhxWVWIEabz4F -- and was told to try here), but I am kinda shooting in the dark: I have been finding online scattered and vague info stating that this card can be made to work with a sparc solaris 10 box (http://old.nabble.com/eSATA-or-firewire-in-Solaris-Sparc-system-td27150246.html is the

After applying 125205-07 on two X4500 machines running Sol10U4 and removing "set sata:sata_func_enable = 0x5" from /etc/system to re-enable NCQ, I am again observing drive disconnect error messages. This in spite of the patch description which claims multiple fixes in this area: 6587133 repeated DMA command timeouts and device resets on x4500 6538627 x4500 message logs contain multiple

So after troubleshooting this for about a week, I was finally able to create a raid 10 device by installing the system, copying the md modules onto a floppy, and loading the raid10 module during the install. Now the problem is that I can't get it to show up in anaconda. It detects the other arrays (raid0 and raid1) fine, but the raid10 array won't show up. Looking through the logs

Dear all, we''re currently looking forward to restructure our hardware environment for our datawarehousing product/suite/solution/whatever. We''re currently running the database side on various SF V440''s attached via dual FC to our SAN backend (EMC DMX3) with UFS. The storage system is (obviously in a SAN) shared between many systems. Performance is mediocre in terms

...61.8 0.0 0.1 13.0 0.1 12.5 4 76 c0t3d0 1042.3 0.0 61.7 0.0 13.9 0.8 13.3 0.8 83 83 c1t0d0 1041.8 0.0 61.7 0.0 11.5 0.7 11.1 0.7 73 73 c2t0d0 1041.8 0.0 61.7 0.0 12.8 0.8 12.3 0.8 79 79 c2t1d0 (actv is less than 1 on c1 & c2 due to si3124 driver not supporting NCQ. I wonder what''s preventing ZFS from keeping the disks busy more than ~80% of the time. Maybe the CPU, see below.) "mpstat 2" CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 0 0 0 0 7275 7075 691 99 146 354...

I?d like to report the ZFS related crash/bug described below. How do I go about reporting the crash and what additional information is needed? I?m using my own very simple test app that creates numerous directories and files of randomly generated data. I have run the test app on two machines, both 64 bit. OpenSolaris crashes a few minutes after starting my test app. The crash has occurred on