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!

Recommended Posts

Hi.

Target is a Synology NAS DS209 , using DSM 3.0-1354.

Short test seems to be successful, copying several smaller files to the target and opening them works fine.

Long run tests @ the weekend. :)

Thx for your work!

Greetz

Jas

Hi Jas, how'd the weekend testing go?

Share this post


Link to post
Share on other sites

Using QNAP TS-410 Version 3.3.6 build 1109T with 4.1.0.247 BETA under 10.6.5 x64

QNAP was added as a portal with two targets sharing the same IP, header CRC. Using friendly initiator naming naa.something-something (minus included). Targets set persistent.

Experienced several system-wide hangs during CPU-intensive tasks (x64 apps) only hard reboot helped.

Let me know if there is any particular test needed.

Arseny

Arseny, please check your initiator name and verify that it meets the standard:

( snip from http://www.faqs.org/rfcs/rfc3980.html )

   The iSCSI NAA naming format is "naa.", followed by an NAA identifier
  represented in ASCII-encoded hexadecimal digits.

  An example of an iSCSI name with a 64-bit NAA value follows:

        Type  NAA identifier (ASCII-encoded hexadecimal)
        +--++--------------+
        |  ||              |

        naa.52004567BA64678D

     An example of an iSCSI name with a 128-bit NAA value follows:

        Type  NAA identifier (ASCII-encoded hexadecimal)
        +--++------------------------------+
        |  ||                              |

        naa.62004567BA64678D0123456789ABCDEF

Let us know if that makes a difference. Thanks!

Share this post


Link to post
Share on other sites

Hi Eric,

Arseny, please check your initiator name and verify that it meets the standard:

( snip from http://www.faqs.org/rfcs/rfc3980.html )

   The iSCSI NAA naming format is "naa.", followed by an NAA identifier
  represented in ASCII-encoded hexadecimal digits.

  An example of an iSCSI name with a 64-bit NAA value follows:

        Type  NAA identifier (ASCII-encoded hexadecimal)
        +--++--------------+
        |  ||              |

        naa.52004567BA64678D

     An example of an iSCSI name with a 128-bit NAA value follows:

        Type  NAA identifier (ASCII-encoded hexadecimal)
        +--++------------------------------+
        |  ||                              |

        naa.62004567BA64678D0123456789ABCDEF

Let us know if that makes a difference. Thanks!

I can hardly believe that using an naa.64 or naa.128 identifier makes any difference. The same goes for the "old " iqn naming, that I am using. These names don't imply any functionality on the initiator side and I don't think that they trigger anything on the target side - or das your own SanMP changes anything internally, when it encounters a naa.64/naa.128 vs. iqn name?

Cheers,

budy

Share this post


Link to post
Share on other sites

Hey budy,

I can hardly believe that using an naa.64 or naa.128 identifier makes any difference.

Probably not, but the potential issue here isn't naa.64 versus naa.128, it's that it appears from the poster's comments that there's a malformed initiator name, which definitely can make a huge difference from target to target.

or das your own SanMP changes anything internally, when it encounters a naa.64/naa.128 vs. iqn name?

Good question. No, SANmp doesn't change anything in that regard. But again, the initiator name, as we've seen (sadly) many times, can in some cases (mostly target dependent) be the difference between a perfectly working environment and a miserable failure. :-)

Share this post


Link to post
Share on other sites

Gentlemen,

Thanks for pointing out. I used naa.52004567BA64678D from your example, re-added persistent targets. Will update you in a day.

Thanks,

Arseny

Share this post


Link to post
Share on other sites

Hi.

Initiator name is here: "naa.7bcc1a5f2795433aa176fd314541c01a".

First of all no problems copying and accessing files.

For me there is one big hook: the speed is very bad.

I tested with aja kona system test, the max write/read speed is about 2MB/s.

We are using a Linksys WRT54g and before the connection problems the speed was at least 12MB/s.

Testing is going on ... :D

Greetz

Jas

Share this post


Link to post
Share on other sites

Hi Eric,

as already pointed out in my other thread, Solaris/OpenSolaris/OpenIndiana COMSTAR doesn't work with 4.1 (247) due to an invalid request at login. I have searched a bit for the parameters that COMSTAR wouldn't negotiate to anything other than the iSCSI specs defaults and found this on the OSol storage-discuss forum:

I upgraded to Solaris 11 Express and GlobalSan 4.0 now also stopped working. Looks like the same type of problem 4.1 has

Share this post


Link to post
Share on other sites

Hi Eric,

Thanks for the feedback Peter. It appears that you resolved that problem over in another thread, yes?

I don't think that's the case. I am successfully using GlobalSAN 4.0 against my OpenIndiana oi_147 targets. SolarisExpress11 is at 151, I think. If I get around, I will install SolExpress 11 as well and check 4.0 against it, but I don't expect any issues there - but who knows…? ;)

Cheers,

budy

Share this post


Link to post
Share on other sites

Got the new driver from Eric by mail (.247-101110-171745). That solved my authentication problem. Did some copying back and forth, plus opened iPhoto 09 library and browsed. I also put the Mac into hibernation and woke it up again. Everything seems OK for now.

Thank's Eric!

:D

Share this post


Link to post
Share on other sites

Got the new driver from Eric by mail (.247-101110-171745). That solved my authentication problem. Did some copying back and forth, plus opened iPhoto 09 library and browsed. I also put the Mac into hibernation and woke it up again. Everything seems OK for now.

Thank's Eric!

:D

Sounds great,

I still have the same problems and can't connect to Oracle Solaris 11 Express. I tried it with the last public beta (globalSAN_4.1.0.247_BETA.dmg) and I still get: Connection error. Code E3FF820B. Invalid request type during Login.

How can I get the new driver (.247-101110-171745)?

Thank's!

Peter

Share this post


Link to post
Share on other sites

Gentlemen,

Is there any way to spot any crashes in operations or review verbose logs of the initiator? I'm still on 247 x64, under 10.6.5, now target is Synology DS411+ DSM3.0-1372

Performance was excellent, but at some point of copying 50+K files (200+GB) the disk just disappeared. It's not in Disk Utility, although globalSAN still shows green persistent target. Deleting the target and re-adding Synology portal doesn't bring the disk back into Disk Utility. Full OS X restart only.

Please advise.

Arseny

Share this post


Link to post
Share on other sites

GlobalSAN 4.1 BETA 247 with Synology DS209+II DSM 3.0-1354 on OSX 10.6.5 :

- Connection OK

- Random Freeze (timeouts) after some seconds/minutes of use

- Freeze everytime I reboot or want to change user

Console error message : "SCSIPressurePathManager : Timed out waiting for inactive/error path to become active"

Previous versions worked fine except freezes at shutdown/reboot

Best Regards

Share this post


Link to post
Share on other sites

Gentlemen,

Trying to drag and drop a large file from my set-up (see above) directly into an application (i.e. 2GB .tiff into Photoshop) disconnects the target and OS X issues 'volume ejected incorrectly' and target disappears from Disk Utility until next reboot.

Where & how to trace this for more details?

Arseny

Share this post


Link to post
Share on other sites

Interval Since Last Panic Report: 1837608 sec

Panics Since Last Report: 1

Anonymous UUID: 6940290A-5AF2-40D4-8F38-363D110A7FC7

Thu Dec 16 15:33:44 2010

panic(cpu 2 caller 0x1a4af23): "IOSCSIParallelInterfaceDevice::CompleteSCSITask: clientRequest is NULL, completedTask = 0x1225bb00\n"@/SourceCache/IOSCSIParallelFamily/IOSCSIParallelFamily-201.0.1/IOSCSIParallelInterfaceDevice.cpp:1261

Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)

0xbb0b3e58 : 0x21b50c (0x5d42fc 0xbb0b3e8c 0x223974 0x0)

0xbb0b3ea8 : 0x1a4af23 (0x1a4cca0 0x1225bb00 0xbb0b3ed8 0x4ff931)

0xbb0b3ef8 : 0x1a50a46 (0x10dcd700 0x1225bb00 0x1 0x2)

0xbb0b3f38 : 0x1a53316 (0x1225e300 0x12dec600 0xbb0b3f78 0x1460b980)

0xbb0b3f58 : 0x54b50c (0x1478ca80 0x13bf07a8 0xbb0b3fa8 0x219114)

0xbb0b3f88 : 0x54b966 (0x1387ac80 0x1 0x0 0x13bf07a8)

0xbb0b3fc8 : 0x2a06cc (0x1387ac80 0x0 0x10 0x13e2ee60)

Kernel Extensions in backtrace (with dependencies):

com.sns.driver.SNSArchitectureModel(1.1)@0x1a4f000->0x1a60fff

dependency: com.apple.iokit.IOSCSIBlockCommandsDevice(2.6.5)@0x140d000

dependency: com.apple.iokit.IOSCSIParallelFamily(2.0.1)@0x1a46000

dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.6.5)@0x13f3000

com.apple.iokit.IOSCSIParallelFamily(2.0.1)@0x1a46000->0x1a4efff

dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.6.5)@0x13f3000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

10H574

Kernel version:

Darwin Kernel Version 10.5.0: Fri Nov 5 23:20:39 PDT 2010; root:xnu-1504.9.17~1/RELEASE_I386

System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 400385743834038

unloaded kexts:

com.apple.driver.MaxTranserSizeOverrideDriver 2.5.8 (addr 0x14ca000, size 0x12288) - last unloaded 42957868345525

loaded kexts:

--cut--

Share this post


Link to post
Share on other sites

I've been unable to use the initiator properly in 10.6 in any version, is there any hope?

Share this post


Link to post
Share on other sites

I've been unable to use the initiator properly in 10.6 in any version, is there any hope?

been running 4.1.247 on 10.6.5 without any problems to thecus 4200

Share this post


Link to post
Share on other sites

I just got my QNAP 459 Pro and setup an iscsi target for storing the library of iPhoto.

When using 4.0.0.204 driver, my mac mini server cannot even estabish the connection to NAS.

Unstall 4.0 and intall the 4.1.0.247 driver, the connection works. Local library copied to NAS.

But when I open the iPhoto and pointing the library to the file in iscsi drive, the iphoto hangup after a few clicks.

My mac server is running on 10.6.5.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×