From owner-freebsd-questions Mon Dec 18 10:21:15 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA10598 for questions-outgoing; Mon, 18 Dec 1995 10:21:15 -0800 (PST) Received: from ceylon.visinet.ca (root@ceylon.visinet.ca [204.225.119.26]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA10590 for ; Mon, 18 Dec 1995 10:21:11 -0800 (PST) Received: from kenya.visinet.ca (kenya.visinet.ca [204.225.119.8]) by ceylon.visinet.ca (8.6.11/8.6.11) with SMTP id NAA20877; Mon, 18 Dec 1995 13:21:31 -0500 Date: Mon, 18 Dec 1995 13:22:17 -0500 (EST) From: Christian Henry To: Iain Templeton cc: freebsd-questions@freebsd.org Subject: Re: No inodes left In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Mon, 18 Dec 1995, Iain Templeton wrote: > Well, I seem to be having a small problem with inodes, I keep receiving > the message (syslog) > > /kernel: uid 8 on /u1: out of inodes > > This is caused by INN (running as uid 8 = news), writing all its junk > files, which I am sure that it didn't M > > I guess what I'm really asking is: How can I increase the number of > inodes, or otherwise fix this problem. Reformatting the disk, although > not preferred here, is an option. The "-i" (number of bytes per inode) parameter, from what I recall, defaults to a value of 2048. If you have to resort to reformatting your disk, try specifying a smaller value (on our news spool drives, I specified "-i 1024"; I suppose that a value of 1536 would also have done the trick, but I was lazy. :-) ). -- Christian Henry e-mail: henryc@visinet.ca Networks Integration Toronto, Ontario support: (416) 488-5352 VisiNet Internet Services Canada data: (416) 488-4009