Date: Tue, 3 Dec 2002 10:56:47 -0500 From: "Brian T. Schellenberger" <bts@babbleon.org> To: Mark Knight <markk@knigma.org> Cc: cfs-users@nsa.research.att.com, freebsd-ports@freebsd.org Subject: Re: cfs and memory usage . . . Message-ID: <200212031056.47931.bts@babbleon.org> In-Reply-To: <QLpsybKY5J79EwnK@lap.knigma.org> References: <200210310412.48667.bts@babbleon.org> <QLpsybKY5J79EwnK@lap.knigma.org>
next in thread | previous in thread | raw e-mail | index | archive | help
You have made my day by merely responding. I have posted to the various lists and never gotten *any* response before; I was really wondering if these were still used. Note that I've tried drastically reducing "NINSTANCES" and I still run into the problem. I find that I can reproduce the problem quite easily by just using the "find" command to do something that actually opens the files in one of my big directories. I would be more than happy to collaborate with you on doing this. The one quasi-useful discovery that I *have* made is that it's perfectly possible to just kill cfsd and start it up again without bothering to detach and unmount and mount and re-attach; it yields "stale NFS handles" in all the shells and/or other programs that have a file open in CFS but is otherwise harmless and for the shells once merely has to cd back to where one already was in order to get everything stable again. This at least lets me avoid crashing or rebooting all the time. On Tuesday 03 December 2002 07:06 am, you wrote: | In message <200210310412.48667.bts@babbleon.org>, Brian T. | Schellenberger <bts@babbleon.org> writes | | >I use the FreeBSD "port" of cfs, and I have noticed that it is very | >greedy in using memory. | > | >Now, I'm a little unfriendly to it now in that I have a number of | > cfs file systems set up but even when I only had one or two it | > would behave the same way: | > | >Memory usage is fine for "normal" activities, but if I do something | > that scans lots of files, such as running a "find" command that | > greps over the files in the CFS area or something, memory usage | > will shoot up to astronomical levels (eg, over 300M or more). | > | >And that memory will never be freed. | > | >This will so exhaust memory that the system will frequently crash | > not long afterwards. | > | >Now, it looks like cfs is *meant* to respond to a SIGALRM and clean | > up memory that's no longer needed, and additionally to go through | > this cleanup automatically every 60 seconds: | > | > signal(SIGALRM,grimreap); | > alarm(60); /* every 60 secs */ | > | >(at the end of main). | > | >But it looks like something is preventing this from happening, or | > the grimreap routine just never agrees to clean up anything. | > | >I know that there are parameters I can tune to use less total memory | > but I'm wondering if other people have seen this behavior and what, | > if anything you did to deal with it. | | Just a note to say that I also have this problem, particularly when | using directories with very large numbers of files. I've also | reported it to the mailing list in the past, without joy. | | You've renewed my interest in finding a fix, I might have a look... | | Cheers, -- Brian, the man from Babble-On . . . . bts@babbleon.org (personal) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212031056.47931.bts>