There are essentially two places where any restriction might be enforced. The first is in the generic kernel code for creating a file. From my reading of the code there is no limit there. The second place is in the code that is specific to the filesystem type, i.e. ext2, ext3, vfat, etc. There seems to be no restriction for ext2 or ext3 filesystems.
There are practical (i.e. performance) limits as well. The time it takes to find, add or delete a file grows with directory size (and it may be non-linear. Shell expansion of metacharacters can result in lists that exceed the maximum size of arguments permitted to a command.
Greetzzz, Mark
"garbage" <garbagedispo...@despammed.com> wrote in message
>>Anyone know what are the practical limits for # of files in a directory >>under ReiserFS ?
>>I have several directories with over 10,000 files, when will it shit >>itself?
Absolutely not. Reiserfs' major claim to fame is its ability to deal efficiently with directories containing 100,000+ files. 10,000 shouldn't be any trouble at all.
On Sat, 29 Nov 2003 16:02:04 +0100, Andreas Steffen wrote: >>>Anyone know what are the practical limits for # of files in a directory >>>under ReiserFS ?
>>>I have several directories with over 10,000 files, when will it shit >>>itself? > Absolutely not. Reiserfs' major claim to fame is its ability to deal > efficiently with directories containing 100,000+ files. 10,000 shouldn't > be any trouble at all.
