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!
Teamscottsmith

Starting over with new drives

Recommended Posts

I have an EVO with both SAN and NAS volumes.  I am replacing drives. 

I created the new Disk Pool successfully. 

I then create a Logical Disk (RAID). 

I add it as a Fiber Channel Target. 

I add it as a iSCSI target.

I use the GlobalSAN initiator to connect to the logical drive.

So far, so good, I think.

Now is when it needs to be formatted.  There seems to be no tool within the EVO to do this, and it seems you are supposed to do it from your OS.  I am Mac OSX 10.10.5, and so I format in DiskUtilities.  I have also done command line diskutil formatting and with the same results.  (I'm not huge into command line stuff, but i figured that one out with some googling)

My new SAN logical drives show up very differently than they used to.  In the EVOShare browser, they appear Black with a Blue center instead of Gray/Green/Red (depending on mount status) that they used to.  The old way had SANmp logo on the icon, and a space above the icon where it showed the mount R/RW status.  The new ones aren't that way.  They cannot be unmounted in ShareBrowser. 

In Disk Utilities, my old SAN Logical Disks show up with the following info

  • Name :     SNS_EVO A-EditSAN1 Media  (OLD Logical Disks)
  •     Type :     Disk   
  •     Partition Map Scheme :     SNS_partition_scheme_v1
  •     Disk Identifier :     disk3
  •     Media Name :     SNS_EVO A-EditSAN1 Media
  •     Media Type :     Generic
  •     Connection Bus :     iSCSI
  •     Device Tree :     IODeviceTree:/
  •     Writable :     Yes
  •     Ejectable :     Yes
  •     Location :     External
  •     Partition Type :     Core Storage
  •     Owners Enabled :    No


The NEW SAN Logical Disks show up with the following info:

  • Name :     SNS_EVO D-teststripe4096 Media (NEW Logical Disks)
  •     Type :     Disk
  •     Partition Map Scheme :     GUID Partition Table
  •     Disk Identifier :     disk2
  •     Media Name :     SNS_EVO D-teststripe4096 Media
  •     Media Type :     Generic
  •     Connection Bus :     iSCSI
  •     Device Tree :     IODeviceTree:/
  •     Writable :     Yes
  •     Ejectable :     Yes
  •     Location :     External
  •     Format :    Mac OS Extended
  •     Owners Enabled :    Yes

Notably, the Partition Map Scheme and the Partition Type are quite different.  What am I doing wrong here?  How do I get the drives formatted in the proper fashion, assuming HFS+/non-journaled is the way to go? 

Any help appreciated.

Share this post


Link to post
Share on other sites

Other questions/comments on tuning . . .

I plan to set my logical disks in RAID 6 configuration, if it makes a difference.  I also am curious about the preferred Stripe Size.  I am considering 1024 on that.  Any reasons pro or against?  What are most people using for that?  Should I crank it to 4096?

I am also going to finally change all my users' connections to a network MTU of 9000 instead of 1500, and change those settings in the EVO as well.  Any reason not to?  Does it actually help?  Should that affect my choice on stripe size? or should I do a custom MTU that is divisible by base2, like 2048, 4096, or 8192?  Does any of this matter at all?

Share this post


Link to post
Share on other sites

Hello!

It looks like the difference you are seeing is that the new SAN volume has not been converted into a SANmp disk. This is accomplished using SANmp Admin, which allows for the SANmp Client software to ensure that only one user has write access to the SAN volume at any given time. This protects the file system from becoming corrupted due to simultaneous writes from multiple users.

For an 8-disk pool, we recommend using RAID-5, which will allow the RAID to recover from a single-disk failure.

The default stripe size on the EVO is set to 128. In our tests, we found this configuration to offer the best overall performance for most situations. In theory, a larger stripe size should offer better performance for large files; however, as media files become more and more massive, the stripe size used appears to have less of an impact on performance. With that said, blanket statements about performance can hardly be made, and it may still be worth testing with different stripe sizes.

The specific MTU value used is not as important as that it matches on the EVO, workstation, and any switches/routers in between. The typical configuration for an MTU value of 1500 for 1GbE, and 9000 for 10GbE.

Please feel free to open a support case if there any other questions or concerns.

Thanks!

Alan

 

Share this post


Link to post
Share on other sites

×