----------
> From: Henrique Pantarotto <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Many files in a single directory
> Date: Sunday, February 28, 1999 3:04 PM
>
> Hello!
>
> I'd like to know if there's any problem having like 15,000 (fifteen
> thousand) directories in one single directory.
>
> I know that the "ls" command would take lots of time to show the results.
> But besides that, is there any reason to avoid doing this?
>
> Is ext2 a nice guy? ;-)
>
>
> Thanks,
>
> Henrique Pantarotto
> Coord. T�cnico Operacional
> CEPAnet Internet Provider
> Web: http://www.cepa.com.br
> Tel. suporte: +55 (011) 5506-8477
> Sao Paulo - Brasil
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
You may want to look into inodes , the way I understand it is, each file
has a index pointer to a 'chunk' of data store somewhere on your hard disk,
and a inode is basically the pointer or link to that file, each file has to
have an inode so you can call the file. Depending on what options you gave
when you installed the system, you have XY amount of inodes. If you run
out of inodes, it spits back an error saying 'no enough disk space' or
something to that effect, even if you have 6 gigs of free space.
In older open linux lite, suse and all the slackware version (probably
every other dist also) give an options when you install, asking how much
inodes per X amount of disk space. Presonally I also get as many inodes as
it will allow to be on the safe side.
I don't know of any man pages or docs off hand.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
