From owner-freebsd-hackers Thu Apr 8 17:58:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B883814FCA for ; Thu, 8 Apr 1999 17:58:08 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40352>; Fri, 9 Apr 1999 10:42:49 +1000 Date: Fri, 9 Apr 1999 10:55:50 +1000 From: Peter Jeremy Subject: Re: Volume managers To: grog@lemis.com Cc: hackers@FreeBSD.ORG Message-Id: <99Apr9.104249est.40352@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: >On Thursday, 8 April 1999 at 15:28:40 +1000, Peter Jeremy wrote: ... >> The `clone filesystem' command supported by >> Digital UNIX ADVfs is _very_ nice for `point-in-time' backups. > The main problem is yet another layer of "where do I get >this byte from?". ADVfs uses the free list within the FS (actually within the file domain). This _does_ mean that clonefset doesn't work on very full, dynamic filesystems. The upside is that it works most of the time and doesn't require reserved free disk space. If there's no free space left, a kernel error message is generated warning that the clone filesystem is no longer consistent (but I don't think it actually inhibits access to it). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message