Christopher (Drashna)

New user: Oddity migrating files with "Max path length" error

New user: Oddity migrating files with "Max path length" error

Hi there.   New user evaluating DrivePool to replace my cheap and aging RAID5 enclosure attached to a WHS2011. I simply used drag and drop to move some of my shared folders from  "H:\ServerFolders\" to "K:\Shared Folders\" and got a few errors about not being able to copy due to file path name being too long. After clicking skip and letting it finish I noticed about 300GB had failed to copy out of 1.5TB.    Now I doubt chances are I was living at the extreme end of the file path limit with 3
ROFLMAO   Amen.      That said, there are two ways to address files: Win32 API (which is what explorer users) and UNC (which is what we use, and robocopy uses, and other utilities).   The main difference between these?  Win32 is legacy, and limited to 260 characters.  UNC is limited to 32k characters.     So, in theory, StableBit DrivePool will never have issues moving files around, or accessing them. But the software you're using MIGHT.      WIndows 10 has a hack to enable log file