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, im currently evaluating the globalSAN iSCSI initiator and have got it working from a Synology nas and a mac mini running 10.10.4 server. I can mount the disk fine and have no issues with it part from resizing my disk in OS X.

1) unmount iSCSI attached disk in disk utility

2) disconnect iSCSI LUN in the globalSAN sys preferences panel

3) grow the ISCSI LUN on the Synology nas (from 3TB to 4TB)

4) reconnect iSCSI LUN in globalSAN sys preferences panel

5) on OS X, remount disk in disk utility and confirm the new disk size 4TB

6) Try to resize disk. Completes after a few seconds but does not resize.

I've tried this with a GUID partition scheme and an Apple partition scheme. Both do not resize.

Has anyone come across this?

  • Like 2

Share this post


Link to post
Share on other sites

February 2017, same issue for me.  Synology DSM v6.0.2  and Global SAN v5.3.0.51 OS X el capitan v 10.11.6    

My original iSCSI LUN was created at 1TB.  As I got full, I expanded the LUN to 2.5 TB.  

The Mac client continues to map to the iSCSI target, but will not report that there is more room available.

 

Share this post


Link to post
Share on other sites

The initiator provides the iSCSI connection, but has no awareness of the file system on the target disk, which is handled only by the operating system.

When a LUN is grown, the underlying disk expands, but the file system on top of it typically has no awareness this has happened. Disk Utility will sometimes allow the partition(s) to be resized, but may require disk repair first.

Share this post


Link to post
Share on other sites

Thanks. 

Seems like OS X won't let you grow (resize) a partition unless it was ORIGINALLY formatted as Journaled.  However, most guidance for a SAN target used in video editing (like Final Cut Pro) recommend to NOT journal, as it would create so slowness.   

As a result I had to drop and recreate the partition on the (newly) large storage space underneath.  

 

Share this post


Link to post
Share on other sites

×