Jump to content

Search the Community

Showing results for tags 'mac'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Covecube Inc.
    • Announcements
  • StableBit Cloud
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic
  • BitFlock
    • General

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. So since switching back to using Windows with DrivePool on my fileserver again a few weeks ago. We have been running into issues with MacOS clients accessing fileshares on it. Browsing and especially creating folders/files, where they create, but then disappear until remount of the share. (One weird thing too is that if you type in a path for a folder and try to browse to it in finder or terminal, then you can't, but if you use terminal to copy a file you know the path of, it can do that.) Been doing a lot of testing, and it seems like MacOS most reliably sees the content of volume with the lowest "\Device\HarddiskVolumeXX\" as seen in resource monitor. The file creation problem can be help by using the SSD Optimizer plugin, and making sure that the volumes marked ssd has the lowest HarddiskVolumeXX. Which worked decently but didn't entirely fix the issuses. I have ended up creating a powershell script, that puts a filewatcher on the entire drivepool, so that every time a folder is created then on all drivepool drives, a folder is create, so no what drive MacOS gets the directory listing from, that folder exists, which seems to have fixed both folder, and somehow file creation problems. https://gist.github.com/eeveelution1313/e25984d7f7ef582357bc8899ca59d25a (As mentioned in the bottom of the script a majority of it is from: https://powershell.one/tricks/filesystem/filesystemwatcher)
  2. Just upgraded my home server from WHS 1 to WHS 2011 and installed Drivepool and Scanner. I have 3 x 2TB drives and a portion of the system drive configured as a drive pool. All disks are formatted as NTFS. I've configured all of the server's shared folders to live on the Drivepool. I'm able to transfer files of any size from a Windows 8.1 client to the server but when I attempt to copy a file from a MacPro (running OSX Yosemite) I get the following error message: The item “XXXX” can’t be copied because it is too large for the volume's format I've seen this message before when using FAT formatted USB disks but not with a network share. Any ideas?
×
×
  • Create New...