>       What is the maximum of NR_INODE and NR_FILE ? Because of an
quoted text
>       "File table overflow" I defined NR_INODE 1024 and NR_FILE 512.
>       Is this to high - could this cause damage to the filesystem ?

These numbers are really only limited by available memory, but beware:
the inode cache is searched linearly every time an inode is accessed.
Upping NR_INODE to 1024 will seriously slow down filesystem
operations.

The 0.99pl10 kernel will automatically allocate more files and inodes
on demand, up to an arbitrary limit currently set at 1024 files and
2048 inodes.  It will also use a hash table to access the inodes, so
that inode lookup will actually be faster than it is currently.

Cheers,
 Stephen Tweedie.
---
Stephen Tweedie <sct@uk.ac.ed.dcs>   (Internet: <sct@dcs.ed.ac.uk>)
Department of Computer Science, Edinburgh University, Scotland.