Date: Sun, 26 Jan 1997 07:55:00 +0100 (MET) From: Martin Jangowski <bsd@birdland.rhein-neckar.de> To: freebsd-questions@freebsd.org Subject: newfs options for newsspool? Message-ID: <Pine.BSF.3.94.970126073440.8295A-100000@birdland.rhein-neckar.de>
next in thread | raw e-mail | index | archive | help
Hi! One of my news machines I am running (P133, 64M RAM, NCR, 2*4 GB Barracuda, FBSD 2.1.6.1) has a single Barrauda as a newsspool. I set it up using "newfs -b 4096 -f 512 -i 2048" in one 4GB partition, to minimize losses due to fragmentation. It worked nicely for some time. I received about 100-120k artikles per day, and everything was fine. Expire took about 5-8h, no prob there. Recently (and without provocation), expire takes 36-48h, the drive is slooooooow (bonnie showed throughputs in the 500-800k/s range, machine in singleuser state), and I have about 1 GB newsbatches in the backlog. The other disk shows nice 4-6M/s... The only difference I'm aware of is the rising volume of the feed, it's around 160-180k artikels a day now, and I had to lower my holding times. Is it possible that the small block size is the culprit? I'm just copying the newsspool to a new barracuda (runs for 8h now, about half done...) with 8k blocksize. I did a search for bad blocks on the news disk, but didn't find any. Any ideas? Martin | Martin Jangowski E-Mail: maja@birdland.rhein-neckar.de | | Voice: +49 621/53 95 06 Fax: +49 621/53 95 07 | | Snail Mail: Koenigsbacher Str. 16 D-67067 Ludwigshafen Germany | | RNInet e.V. Rhein-Neckar Internet |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.94.970126073440.8295A-100000>