Jump to content
SNS Users' Forums
  • Announcements

    • Eric Newbauer

      Follow SNS on Twitter!

      Get notifications via Twitter! Looking for instant updates? We're now also announcing new versions and beta programs via Twitter. Follow Studio Network Solutions on Twitter. Thanks!

Crosscreek

Members
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Crosscreek

  • Rank
    Member
  1. I had major problems with data corruption on Open-E iSCSI Enterprise.
  2. Studio Network Solutions sells SANmp, which is an alternative to Xsan. Odd you didn't mention it since this is their forum.
  3. Glad to see all the activity here! I did some tests recently with the free targets and a Mac Pro w/ 10.5.2: globalSAN 3.2.0.15: Openfiler 2.2 - Works and is really fast (around 100 MB/s) but causes the Mac to crash during large transfers. FreeNAS .686.3 - Works but is beyond slow. Like 3 or 4 MB/s. globalSAN 3.3.0.35 Openfiler 2.2 - Can connect but can't partition. Disk Utility just hangs. Openfiler console gives me scsi error messages. FreeNAS .686.3 - Works rather well! Only 40 MB/s, but this is likely a non-iSCSI related problem as I get similar speeds using AFP, SMB, or FTP services. I'll test out the new one when I can.
  4. GUID, Apple Partition Map, or MBR? Couldn't picking the wrong kind screw up the target's RAID?
  5. I'd like to let everyone know that it seems this limitation no longer exists with OSX Leopard 10.5. I created a 3.5TB partition in Leopard no problem using Open-E (which only shows as 2TB in Tiger). After creating the partition in Leopard, I can connect to it with Tiger and it now sees it as the full capacity! The Finder is showing a 3.45TB disk, but Disk Utility still says it's only 2.0TB. Very strange. I guess I'll see what happens if I try to copy more than 2TB of data to it.
  6. Any more info on this? Have you tried formatting HFS with disk utility yet? What kind of performance are you getting?
  7. Transferring to and from a local array. The one I've mostly been testing is currently my editing workhorse. It's a 4-disk SATA array using Disk Utility's RAID-0. I'm a thousand percent certain that's not related. I've also tested it using a different client box (PPC G5 w/ a Highpoint 8-disk local RAID-5) and the results were the same. I'm working with Wasabi quite a bit. They've been great, but they'll blame the initiator whenever possible. The only problems I've been able to reproduce using the Windows Initiator is the MC/S write-speed problem. And your advice to downgrade the 3ware firmware has resolved that. I think I'm just going to have to send them my flashware chip and see if they can reproduce the results.
  8. Ryan, thanks a lot for that information. It definately made a difference. So far I only tested a hardware 3ware RAID-0, but the performance bottlenecks dissapeared. MC/S is working as well. And I'm getting 150MB/s write and 180MB/s read. The only reason I'm not jumping for joy is that during disk transfers, the target has a kernel panic and reboots itself. But this helps narrow things down. Thanks again.
  9. 3ware RAID-0 seems affected as well. Software RAID-0, using the Marvell instead of the 3ware, and using a single connection (not MCS) is the only configuration that works fast and flawlessly. Software RAID-5 also works without any issues. But the write speed is somewhat slow. Multipathing/MCS issue exists no matter what SATA controller or RAID configuration I use. The 3ware card has the latest firmware that came with the 9.4.1.2 release. I also tested another firmware version (I have two of the same exact cards available) from Oct 06. It didn't affect anything. I'm going to try and test the multipathing/MCS using WinXP and the MS Initiator. If it still doesn't work right, then I'll know that there are issues with my target and not the initiator.
  10. Thanks for all the help Ryan. I can get it working great w/ software RAID-0. But when I use my 3ware card's RAID-5, I have problems when using your initiator on my Mac Pro. Write speed is well below expected, and transfers will sometimes freeze up temporarily. And sometimes the target will crash and reboot itself during those freezes. Using the same client machine, if I reboot into Windows XP (using boot camp) I don't have any of those problems whatsoever with the Microsoft initiator. I get a full 100 MB/s without any hiccups. Also, multipathing doesn't seem to be working right with globalsan. Speeds are around 150 MB/s, but it freezes during transfers. This occurs whether I use RAID-0 or RAID-5. I haven't been able to test multipathing with WinXP because I don't know how to set that up. Can you recommend a version of IP-SAN which might have better compatibility with your initiator? I jumped from 2.1 to 2.3.1. I never tried 2.2 or anything else in between. And could the fact that I don't have SANmp have anything to do with these problems? I know I need it to safely use multiple clients. But right now I'm just testing a single client (and I'm plugging straight in - no switch or anything). Thanks again.
  11. Saying I solved it was premature. Not even close. Could someone help me with any unusual non-default settings I should set on the target to ensure compatibility with the globalSAN Initiator? Is it okay to format using HFS+?
  12. FYI, I tested out the demo for the new Open-E iSCSI R3. I couldn't re-create the issue with it. I copied 800GB of files and it didn't lock up. Also tested Open-E DSS, and that too seemed to work fine. But it's still shows volumes >2TB as 2TB.
  13. I solved it. Wrong settings is all it was.
  14. One of our iSCSI targets uses Wasabi IP-SAN. I recently upgraded the target to the latest software. I can connect to it with globalSAN, and it works. But I get terrible performance. About 40MB/s write, and only 10MB/s read. If I use ATTO XtendSAN, the results are a lot different. I have a very strong desire not to go back and use XtendSAN. Is there anything I can do to fix this issue? Are there any settings I should be aware of?
×