According to Joe Cooper:
> I've been running some squid benchmarks here using polygraph, and have
> found that 2.2.14 (or possibly squid 2.2.STABLE5) seems to have a huge
> inode leak.
I've seen this too. It's irritating to have to reboot my colo server
twice a week; it's like I'm using NT or something. :-(
> The rate of growth is about 30-60 per second depending on how much
> data is flowing in and out on the network.
My observed rate is more like one per minute, with occasional faster
bursts. I haven't managed to correlate any particular activity to the
bursts.
To summarize what we know so far:
* The leak affects 2.2.13 and 2.2.14, at least.
* The leak occurs when the high-activity filesystem is either ext2
or reiserfs, so it's probably in the fs-independent code.
* The leak rate varies depending on system activity.
Anything else?
--
Chip Salzenberg - a.k.a. - <chip@valinux.com>
"He's Mr. Big of 'Big And Tall' fame." // MST3K
-
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/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:13 EST