Messages in this thread | | | From | Oleg Drokin <> | Subject | Re: [patch] inode leakage again | Date | Fri, 5 Feb 1999 12:51:45 +0300 (MSK) |
| |
Hello!
> Oleg can you confirm me that this my new patch against 2.2.1 (or > 2.2.2-pre1) fix everything for you? I can't produce lockups or leakage > anymore here. I cannot reproduce neither lockup nor leakage. But I get "grow_inodes: inode-max limit reached" and I cannot access any file anymore, I get above message again and again until I do sync. Not very good result, I think
> _Don't_ be happy (maybe this time Murphy will hear my words? ;) As you wish ;)
> Now there's a secondary major problem that I am going to fix now. The > problem is that inodes seems to stay busy even if they are unused from > your proggy so you'll get many `inode-max limit reached' messages (but > the system remains perfectly stable here and you can increase inode-max > to workaround temporarly the problem). Seems that I hit it.
Bye, Oleg -- [RAVE *SUCKS* TEAM] [Team $Ui(iDE] [Trans-M Must Die!] [Sepultura Fans Team] [Tolkien forever team]
- 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/
| |