Can't share mounted sparsebundle...

Discussion in 'OS X Mountain Lion (10.8)' started by tarjan, Aug 19, 2012.

  1. tarjan macrumors regular

    Joined:
    Aug 11, 2006
    #1
    Upgraded to ML and my sparsebundles are no longer sharable.

    Much like going from SL to Lion resulted in fat32 shares still showing in the afp file sharing preference pane, but not working. Upgrading to ML is showing that my mounted sparsebundles are shared, but nothing is showing on my other macs. Sharing regular files/folders works fine.

    I can't find any errors anywhere. sudo sharing -l shows the sharepoints as well.

    Sparsebundles are just mounted as regular mountpoints, double click and go.

    I really need to get this working again ASAP. Any help would be VERY appreciated.
     
  2. wolfish17 macrumors newbie

    Joined:
    Aug 21, 2012
    #2
    Same problem

    I have the same problem with sparse bundles and have the following odd additional observations:

    Mounted external drives on Thunderbolt or Firewire share fine.

    Mounted external drives from SD card or USB2.0 fail (i.e do not show up on client machines.)

    Mounted .dmg volumes fail to show up.

    Mounted truecrypt volumes fail to show up.
     
  3. tarjan thread starter macrumors regular

    Joined:
    Aug 11, 2006
    #3
    .1 didn't solve the problem, which really sucks.

    One interesting thing is that ML *DID* fix the issue of SMB sharing non hfs+ volumes. So if you have maczfs or a fat32 partition, share away without resorting to installing samba.
     
  4. wolfish17 macrumors newbie

    Joined:
    Aug 21, 2012
    #4
    I can't believe this isn't causing a bigger fuss. Perhaps it isn't hitting all ML installations? I'm going to try to find other ML machines (maybe cleaner than mine) to test this on.
     
  5. wolfish17 macrumors newbie

    Joined:
    Aug 21, 2012
    #5
    The sparsebundle sharing problem was demonstrated to me on a fairly clean VM installation of ML. Upgrading that installation to 10.8.two seemed to fix the problem. In both cases communication was only between VM and the host not over a LAN.
     
  6. tarjan thread starter macrumors regular

    Joined:
    Aug 11, 2006
    #6
    Well that is good and bad, if that revision fixes the problem, I can be backing up my various macs again in a few weeks. The bad is... lets just hope nothing breaks in the mean time!
     
  7. tarjan thread starter macrumors regular

    Joined:
    Aug 11, 2006
    #7
    Here is a temporary solution(ish): https://github.com/joshado/liberate-applefileserver

    This actually tricks the file serving process into thinking all drives are hfs+, therefore available for direct sharing. Wish I had found that a long time ago, wouldn't have needed to mess with sparsebundles and strange sharing setups etc.

    Of course it means I have to re-do my backup from scratch, so there go a couple hours for my different systems, but that's small change compared to data loss.
     
  8. kakalaka macrumors newbie

    Joined:
    Nov 30, 2011
    #8
    Unfortunatelly the above workaround does not work for me (I've tested it on 2 computers)

    However without trying the above you can still connect to your shared sparsebundle share points, but only via SMB/CIFS.

    so just type cmd+K and enter your computer ip:

    smb://xxx.xxx.xxx.xxx
     
  9. tarjan thread starter macrumors regular

    Joined:
    Aug 11, 2006
    #9
    Not sure why it doesn't work for you? Any errors? Just curious really.
     

Share This Page