Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, January 16, 2016 1:43 AM
Rsyncing Linux directories and files to Windows 10 Home. Errors on a number of directories that have > 13 levels from C:\
What is the limit for directory (folder) levels in Windows 10? Is there a way to configure so that I can have more directory tree levels?
All replies (3)
Sunday, January 17, 2016 7:24 PM âś…Answered
You could try the command line tool "robocopy" which is included in windows 10, and supposed to handle long file pathes.
As I have never used this myself, I can not give you anymore advice.
Saturday, January 16, 2016 1:05 PM | 1 vote
The problem is not the directory depth, but the path length. A lot of Windows programs still have a limit of 256 characters for the path (and sadly Explorer is one of them).
So you could try a different program to sync the files back to windows (as the file system DOES support much much longer pathes), but then you may not able to open them.
Here is more information:
Saturday, January 16, 2016 10:16 PM
Read through the documentation provided. Reinforces my "love" for MS products. See comments.
The documentation refers to the ability to use "long" path names with \?\ switch to override MAX_PATH, but I am not clear how to utilize in the context of rsyncing my unix created files to a Windows 10 host. Other option would be to rename each of the erroring paths to shorter less descriptive names, which I rather not do.
What I'm attempting is to move all user files to a central Windows 10 host directory. From there I can then share the files to Virtualbox guests. Goal is to avoid duplication across guests, provide access across network, and reduce the storage requirements for each VB guest.
Any ideas or suggestions to implement this in Windows 10?