From owner-freebsd-isp@FreeBSD.ORG Tue Mar 25 23:44:19 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 83D8937B404 for ; Tue, 25 Mar 2003 23:44:19 -0800 (PST) Received: from exhsto1.se.dataphone.com (exhsto1.se.dataphone.com [212.37.6.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CB2B43FAF for ; Tue, 25 Mar 2003 23:44:18 -0800 (PST) (envelope-from patrik.forsberg@dataphone.net) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 26 Mar 2003 08:44:15 +0100 Message-ID: <8F69143C0B1A9F4D95AFC58CF69877E54E61FD@exhsto1.se.dataphone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: update filesystem problems - still unsolved but new evidence Thread-Index: AcLzZxpKdlsAqbudQpOEFBID+ebv3wAAzueA From: "Patrik Forsberg" To: "Arie J. Gerszt" , X-Spam-Status: No, hits=-3.8 required=5.0 tests=QUOTED_EMAIL_TEXT,QUOTE_TWICE_1 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:44:20 -0000 X-List-Received-Date: Wed, 26 Mar 2003 07:44:20 -0000 > > 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. Id try a "du -hsx /" and see what exacly is taking up the space. Move out /etc/named to /var/named or something and reconfigure named for it. Do a "find / -x -iname "*core*" -print" and see if you have and stale core-files somewhere taking up the space - and if so erase them. > > Any help in solving that very appreciated. > >=20 >=20 > Have you tried removing logs, and rebooting the daemons they=20 Um.. he have a seperate /var so I dont think that could be the problem.. >=20 > Might work.. might not.. just a thought.. I didn't read the=20 > whole thread, so its a stab in the dark :) Its a few things to try.. but if it is still growing something is taking up some major space by now and I dont think just enlarging the disk would fix this permanently. Good luck, patrik