> >>and I cannot access any file anymore, I get above message again and again
> >>until I do sync.
> >Bingo. When you do sync you get everything back ok?
> was failing with my last fix is exactly due the dirty inodes that was not
> flushed do disk.
>
> This my new patch should fix all your inode problems. These fixes are
> needed also in the case we'll move the inode allocation to the slab
> instead of getting raw pages. The only differences is that if we'll make
> the inode pool shrinkable we will be allowed to go over inode-max without
> harming the system forever (just removing the return NULL if the `if
> (nr_inodes > max_inodes)' fails).
This patch seems to be good. At least I cannot force 2.2.1 with it
to hang or eat memory on my tests. I am almost sure that it'll
perfectly surives my realworld example too, but I can try it only in the
Monday evening.
Thank you for your work.
Bye,
Oleg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/