From owner-freebsd-hackers Fri Mar 3 14:53:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 47C7A37B5E5 for ; Fri, 3 Mar 2000 14:53:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA02107; Fri, 3 Mar 2000 14:52:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003032252.OAA02107@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Beattie Cc: Michael Bacarella , Julian Elischer , David Scheidt , freebsd-hackers@FreeBSD.ORG Subject: Re: Copy-on-write filesystem In-reply-to: Your message of "Fri, 03 Mar 2000 14:49:48 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Mar 2000 14:52:46 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > No one will appreciate that happening to their "permanent" data, > > especially if the OS decides that the best way to get out of debt is by > > deleting a file :) > > Actually, since this is copy-on-write, you do not need the block, until > you write. If you need to make a copy, it will be on a write system call > (possibly an inode update), just fail the write ENOSPC or whatever. Or am > I missing something simple here. Failing a write into the middle of an existing file with ENOSPC is going to break any application that's not expecting a potentially sparse file... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message