Date: Thu, 14 Aug 1997 09:01:09 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: *really* slow rm on an async file system? Message-ID: <199708141301.JAA06376@lakes.dignus.com>
next in thread | raw e-mail | index | archive | help
If you remember; a few weeks ago (well, several now, actually) I initiated a discussion about 2.2.1 and news - how I had thought it expire was working slower in 2.2.1 then previous versions... At that time; there were several recommendations: 1) Mount the file system async (done) 2) Bump NBUF (now bumpped to 128) 3) the "control" group had received a massive swamp of control messages; making for quite a large directory (corrected by removing all the files in the /usr/spool/news/control directory.) This worked well for some time; but... the problem has resurfaced. So - I looked in /usr/spool/news/control - sure enough, there are quite a few files.... So - I did a "rm *" there; to removed them and rebuild my history file. It's now been 15 minutes; the "rm *" hasn't completed... (this is 2.2.1+ on a 386/33 w/ 8meg of memory... it's slow; but not *that* slow...) I can't stop the process (control-C doesn't get it), and, although an "echo *" worked in that directory just a second ago, it also hangs there now... Does this point to a potential buffer deadlock somewhere? I did a ps -gaxl, to see where rm was waiting; but it doesn't show up in the list... An interesting data point; I brought the machine to single-user and did an "ls -l" in my control directory. This bombed out due to lack of swap space... and echo * didn't complete either... so this could all simply be a swapping contention issue... Just F.Y.I. - - Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708141301.JAA06376>