From owner-freebsd-isp@FreeBSD.ORG Tue Mar 25 23:12:35 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 777ED37B404 for ; Tue, 25 Mar 2003 23:12:35 -0800 (PST) Received: from alcatraz.wolfpaw.net (alcatraz.wolfpaw.net [216.194.99.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 8190E43F3F for ; Tue, 25 Mar 2003 23:12:32 -0800 (PST) (envelope-from admin-lists@wolfpaw.net) Received: (qmail 3246 invoked by uid 0); 26 Mar 2003 07:12:30 -0000 Received: from unknown (HELO wolf) (216.123.201.128) by 0 with SMTP; 26 Mar 2003 07:12:30 -0000 From: "Wolfpaw - Dale Corse" To: "Arie J. Gerszt" , Date: Wed, 26 Mar 2003 00:24:32 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: X-Spam-Status: No, hits=-12.2 required=5.0 tests=IN_REP_TO,MSGID_GOOD_EXCHANGE,QUOTED_EMAIL_TEXT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: RE: update filesystem problems - still unsolved but new evidence X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 07:12:39 -0000 X-List-Received-Date: Wed, 26 Mar 2003 07:12:39 -0000 [SNIP] > sweep is the av scanner for qmail (user id 85). Strangely, > the av scanner > does not > sit on /, rather /usr/ > > An "du -s /" doesn't seem to work either; but a "du /" works. > > So it shows, that something over night or a regular process > is filling /, > because > I cleared 3 MB yesterday as mentioned above and now again > it is full. > > I am running the du / pipeing it into a file (on another > partition of > course) and > will sort it quickly. Maybe this gives a clue too. > > Any help in solving that very appreciated. > Have you tried removing logs, and rebooting the daemons they belong to? For example, apache logs can get HUGE, and I seem to recall a simular bug on a box we had, in which you would blow away the log file, and if it was big enough, it would not free the space correctly for some reason until apache was restarted, if I recall syslog had some simular issues. Either killall -KILL (then restart it), or clean up and reboot your box.. Might work.. might not.. just a thought.. I didn't read the whole thread, so its a stab in the dark :) Good luck :) Dale. -------------------------------- Dale Corse System Administrator Wolfpaw Services Inc. http://www.wolfpaw.net (780) 474-4095