On Fri, 9 Jun 2000, Reid Sutherland wrote:
> Hi Mario and thanks for the prompt reply.
Hi Reid,
I think the problem is not related with the number of files/dir
you've in your system. Reading the inode.c you'll see that some inodes
doesn't correspond to files/dir in your disk; they're empty inodes.
No, it's not one inode per file/dir. They're connected as a
linked list to represent the entire file, that is, several inodes for
one file (direct pointers, single indirect pointer, double indirect
pointer and triple indirect pointer), where the indirect pointers point
to next file blocks as needed.
Maybe your problem is in other point rather than filesystem
itself - just a guess!
hth,
[]s,
Mario O.de Menezes "Many are the plans in a man's heart, but
IPEN-CNEN/SP is the Lord's purpose that prevails"
http://curiango.ipen.br/~mario Prov. 19.21
http://www.revistalinux.com.br
