Um, maybe... If you simply increment with a batchfile using ASCII names for the directories, such as:
x:\a x:\b etc., through x:\12345678901234567890........ with no subdirectories, I wonder how long before you reach a limit. I haven't run across documentation regarding that. Kurt On Tue, Feb 12, 2013 at 12:34 PM, AVJO - Vegh Jozef <jozef.v...@avjo.sk> wrote: > You will rather reach the max path length than reaching the max adressable > directories on NTFS. > > Imagine the following: drive x: > > So path would be x:\a\b\c... Etc. > > So would be than 260 / 2 - 1 = 129 levels... > > Jozef > > > > > On 12.2.2013, at 21:23, Kurt Buff <kurt.b...@gmail.com> wrote: > >> A directory is just another kind of file. >> >> What's the max number of directories in any given directory? By that, >> I mean only the top-level directories, not counting the >> subdirectories. >> >> It would be interesting to test this with a simple batch file to start >> creating subdirs in a directory and see if/when it blows up. >> >> Kurt >> >> On Tue, Feb 12, 2013 at 11:52 AM, Chinnery, Paul <pa...@mmcwm.com> 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:kurt.b...@gmail.com] >>> 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 listmana...@lyris.sunbeltsoftware.com >>> 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 listmana...@lyris.sunbeltsoftware.com >> 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 listmana...@lyris.sunbeltsoftware.com > 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
