Did you added the b_count = 0 in bforget() (buffer.c)? If not search for a
patch posted by Linus on the list. Such bug in 2.2.4 could cause proggy to
go oom after deleting large files.
>Could it be connected to the recent change in inode memory allocation
>algorithm (two instead of one page at a time)?
Definitely no. To be paranoid enough you could show me your
/proc/sys/fs/inode-state though ;).
Andrea Arcangeli
PS. Thanks again to MikeG for forwarding these emails while the list
was down here ;).
-
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/