From owner-freebsd-questions Fri May 21 5:44:38 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hera.webcom.com (hera.webcom.com [209.1.28.42]) by hub.freebsd.org (Postfix) with ESMTP id 583051531A for ; Fri, 21 May 1999 05:44:31 -0700 (PDT) (envelope-from graeme@echidna.com) Received: from eresh.webcom.com (eresh.webcom.com [209.1.28.49]) by hera.webcom.com (8.9.1/8.9.1) with SMTP id FAA00867; Fri, 21 May 1999 05:44:31 -0700 Received: from [204.143.69.17] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 34287104; Fri May 21 05:40 PDT 1999 Message-Id: <37457F50.ED2@echidna.com> Date: Fri, 21 May 1999 08:44:16 -0700 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: Juergen Nickelsen Cc: freebsd-questions@freebsd.org, info@boatbooks.com Subject: Re: File system gets too fragmented ??? References: <374567E9.4854@echidna.com> <3745515C.45EBC1F6@tellique.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Juergen Nickelsen wrote: > > Graeme Tait wrote: > > > In addition, I have a new problem: fsck -n now reports: > [...] > > ** Phase 4 - Check Reference Counts > > UNREF FILE I=48947 OWNER=open MODE=100644 > > SIZE=13109876 MTIME=May 19 21:55 1999 > > CLEAR? no > [etc.] > > It looks like you are running fsck on a read/write mounted file system > -- at least if you did, it could look exactly like this. (The reason is > that files may be open, but have no links in the directories; when the > process that has the file open exits, the file will be freed > automatically.) > > fsck gives meaningful results only on unmounted file systems or on file > systems mounted read-only, e. g. when booted into single-user mode (with > the boot flag -s). Thanks - I see the problem now. There were a whole bunch of ftpd tasks that were hanging around from aborted transfers. I killed them and the 'fsck -n' is now OK. This filesystem has very little write activity apart from periodic ftp uploads and expansion of the uploaded archives. Formerly I had set sysctl -w net.inet.tcp.always_keepalive=1 to clean up these lost souls (why doesn't ftpd time itself out?), but somehow this got forgotten in a reboot. -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message