From owner-freebsd-questions@FreeBSD.ORG Mon Mar 29 08:08:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35ED516A4CE; Mon, 29 Mar 2004 08:08:54 -0800 (PST) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9832A43D3F; Mon, 29 Mar 2004 08:08:53 -0800 (PST) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) i2TG8jqW690270; Mon, 29 Mar 2004 18:08:46 +0200 Date: Mon, 29 Mar 2004 18:08:44 +0200 (CEST) From: Lukas Ertl To: "Greg 'groggy' Lehey" In-Reply-To: <20040329080752.GU52771@wantadilla.lemis.com> Message-ID: <20040329180252.A672@korben> References: <200403290737.i2T7bd1g019407@lk106.tempest.sk> <20040329080752.GU52771@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: imap 4243; Body=0 Fuz1=0 Fuz2=0 cc: Ludo Koren cc: questions@FreeBSD.org Subject: Re: growfs on vinum volume X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 16:08:54 -0000 On Mon, 29 Mar 2004, Greg 'groggy' Lehey wrote: > On Monday, 29 March 2004 at 9:37:39 +0200, Ludo Koren wrote: > > It finished with the following error: > > > > growfs: bad inode number 1 to ginode > > > > I have searched the archives, but did not find any answer. Please, > > could you point to me what I did wrong? > > You trusted growfs on 5.2.1 :-) > > growfs is suffering from lack of love, and presumably you had a UFS 2 > file system on the drive. It's only recently been fixed for that, in > 5-CURRENT. Well, this particular bug is not fixed right now, I fixed a different one. The 'bad inode number 1' problem happens when you grow your filesystem so large that the cylinder group summary needs to allocate a new block. I haven't found a fix for that yet, but interestingly enough, you should now run fsck on that filesystem, and *after* that, you should be able to grow that filesystem successfully (yeah, it's some kind of voodoo). cheers, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/