Search the Community
Showing results for tags 'share'.
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)
I'm running drivepool on Windows 2012 R2. I noticed slower than usual performance on a share stored on the drivepool. I' utilized LAN speed test to test out some of my suspicions. I consistently get 800+Mbps/~100MBps on a share that is on the raw hard drive that is part of a drivepool. However when I do the same test on a folder in the drivepool (actually on the virtual drivepool drive), performance consistently lags down to 600Mbps/~70MBps. I've enabled all the Diskpool I/O performance options (network, etc...) Looking at the performance monitor on Drivepool UI, it shows its reading the file at what should be quicker performance, e.g. 150+MB/s. Any input? I've attached pictures showing performance tests, etc...