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!

Search the Community

Showing results for tags 'GlobalSAN'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • SNS Resources
    • Welcome to the Forum
    • Current Software Version List
    • Knowledge Base
    • SNS Product Announcements
  • Public Discussions
    • SANmp, iSANmp, EVO, and ShareBrowser
    • globalSAN iSCSI Initiator and globalSAN Xtarget Storage Server

Found 5 results

  1. Hey SNS, I had posted this on StarWind's forums, as I think this is an issue for them, but could you a look and see if this could be an issue on GlobalSAN/iSANmp's side? https://forums.starwindsoftware.com/viewtopic.php?f=5&t=4577 Thanks!
  2. Using iSCSI initiator 5.2 (and 5.3) on Yosemite with a Western Digital EX4 NAS I get an Error whenever I reboot the iMAC and try to copy, delete or edit any files on the iSCSI partition "The error can't be completed because an unexpected error occurred (error cod 50)" is returned. Disk sleep is disabled on both OS-X and the NAS but given this can occur after rebooting OS-X disk sleep seems irrelevant. As a test I've created the iSCSI partition, copied a few GBs of data, rebooted and then received the error after reboot. At no point has the Mac been allowed to "sleep". The WD EX4 NAS works fine for two other iSCSI partitions connected to two other Windows machines. Normal browsing of a Public share on the NAS also works fine with standard RWD operations being successfully completed. Anyone else had similar behaviour?
  3. We've been struggling with GlobalSAN under OS X 10.7.5 server talking to a Dell Equallogic SAN and wanted to share for anyone else who will be experiencing problems. If you are not aware, the Equallogic is an enterprise class SAN device. On one site we have two physical boxes in a single group providing over 150TB of iSCSI storage. Each device has multiple gigabit connections into our network backbone, and each gigabit link has it's own IP address. We bought a license for GlobalSAN so that our OS X fileserver could utilise 10TB of storage for Mac clients using AFP. Everything will work fine, until the Equallogic performs a load-balancing operation which basically disconnects a client causing it to reconnect, at which point it will be directed to the interface that is least busy. When using GlobalSAN, this is effectively similar to someone yanking out the USB cable of an external USB drive, then quickly connecting it back in again. The problem is that from OSX's point of view, if the reconnection happens before the drive is dismounted, this results in a second volume with ' 1' appended to the end. i.e. if your iSCSI volume is called 'Data', you will end up after such an operation with a volume called 'Data 1' mounted, then 'Data' disappears. The problem is this breaks Apple's file server which behaves as though the volume was simply unplugged. *Sometimes* it recovers quickly enough to continue sharing files, however any sessions get disconnected. This is obviously extremely disruptive for all Mac clients who get disconnected from the fileserver and in some cases have to reboot. Other times it doesn't, which causes a denial of service to our users. We reboot the server in this case, but sometimes the server freezes on reboot and the crash report indicates the problem was the GlobalSAN extension. We are assuming that it basically has difficulty coping with the Equallogic load-balancing operation. When it recovers, we repeatedly get the error in the system log: kernel: GLO Warning: error during the recoveryThe connection is also orange in the system preference. We did contact GlobalSAN support (#208219) however a resolution was not forthcoming. Due to the amount of complaints from our users we had to find an alternative solution, so we have purchased a license for the ATTO iSCSI client, and we have been running this now without a single issue for the last two weeks or so, so this would suggest a problem with the GlobalSAN client. It's a shame because this is literally the only issue we have had with the GlobalSAN software. Hope this is of use to Equallogic users.
  4. Good day all, During our globalSAN qualification testing noticed that the globalSAN version 5.2.0.429 has a issue with iSCSI logout. A prior version was tested as well (5.1.1.423) and this contains the same bug as well. The missing globalSAN code or bug is: when clicking the "disconnect" button in the globalSAN.pref.pane a logout request is NOT sent to the target array! When this occurs most arrays log a **ERROR** unexpectedly closed. We have tested this extensively The order of disconnect for globalSAN should be the following: 1. "disconnect" button event; globalSAN should then send a iSCSI Logout request to the target array 2. the Array will acknowledge that the initiator has made a logout request. 3. The target array will close the connection at the initiators request Since this is a paid for product and the above is basics of the iSCSI protocol RFC standard. When can the globalSAN Mac community expect this to be fixed? thank you
  5. Hi I downloaded and installed GlobalSAN 5.1.1.423 on a trial basis on my Mac Mountain Lion system, but there is no icon for the application in my System Preferences. I see that similar posts have been made in the Forum, but none of the proposed solutions helped me. I do not currently have any previous version installed. Do I need to install any other software or do anything else? Thanks. Brian
×