According to MS it can be max 260 characters long. Source MSDN: In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path isMAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is "D:\some 256-character path string<NUL>" where "<NUL>" represents the invisible terminating null character for the current system codepage. (The characters < > are used here for visual clarity and cannot be part of a valid path string.)
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx However mapping fileshares as local drives could cause that you can create filepaths longer than 260 characters from the clients. Then you might have issues backuping these directories / files from the server. Regards Jozef On 12.2.2013, at 20:52, "Chinnery, Paul" <[email protected]> wrote: > The path isn't too deep: E:\convert\0000000\0000\0000\0000 and from that > point, other folders are created usually on the order of 000000xxxxxx. > Probably on the order of 2+ million folders right now. At the end, though, > it will be 4+ million easily. > > -----Original Message----- > From: Kurt Buff [mailto:[email protected]] > Sent: Tuesday, February 12, 2013 1:20 PM > To: NT System Admin Issues > Subject: Re: file limitation error > > Aside from path length, which others have already mentioned, if you have more > than 10k files in a directory things will *really* start to slow down. > Whether this will start to generate the errors you're seeing is unknown to > me, but I wouldn't be surprised. > > Just FYI - the Win32 API only supports path lengths of approximately > 254 characters (I say approximate because there are some interesting > oddities) - this is different than the native Windows API, which allows for > much longer path lengths, something on the order of 32768 characters, IIRC. > For example, copy.exe and xcopy.exe both use the > Win32 API, whereas robocopy.exe uses the Native API, and will copy (and > delete) those longer names. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
