> I got the above error, which, I have on good authority, "cannot
> happen".
>
> The machine hung up, I did a hard reboot. There is nothing in the
> logs, no stack dump, nothing.
The "no free inodes" message is quite possible, but not likely under
normal circumstances. The first thing to check is the value you're using
for max_inodes -- you may need to increase it beyond the default (3072
for 2.0.32 I think.)
How much memory do you have on the machine? 4000 inodes is good for a
32M machine, maybe 6000 for 64M.
Regards,
Bill