From owner-freebsd-fs Thu Oct 28 10: 0:13 1999 Delivered-To: freebsd-fs@freebsd.org Received: from login-2.eunet.no (login-2.eunet.no [193.71.71.239]) by hub.freebsd.org (Postfix) with ESMTP id 3151214C99 for ; Thu, 28 Oct 1999 09:59:58 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (mbendiks@login-1.eunet.no [193.71.71.238]) by login-2.eunet.no (8.9.3/8.9.3/GN) with ESMTP id SAA81361; Thu, 28 Oct 1999 18:59:54 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id SAA27855; Thu, 28 Oct 1999 18:59:54 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Thu, 28 Oct 1999 18:59:53 +0200 (CEST) From: Marius Bendiksen To: Bernd Walter Cc: freebsd-fs@FreeBSD.ORG Subject: Re: Journaling In-Reply-To: <19991027193200.A52144@cicely7.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm also intersted in having a way to shrink an FFS filesystem, but it is > much more difficult than growing and you have to rename inodes which is not > always good. > At this moment I'm thinking of some ways to retain the inode numbers. > In the more common case your system is getting to small and you want to > have another HDD added - so only be able to grow does make sense. This is another place where (shoot me if I'm wrong), stacking layers would be handy. One could make a stacking layer to provide inode remapping. Or, if this is the wrong approach, one could add code to FFS to allow inode remapping metadata. This way, one could rename the physical inode and update the mapping. Or am I way off mark here? Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message