Date: Fri, 03 Mar 2000 14:52:46 -0800 From: Mike Smith <msmith@freebsd.org> To: Brian Beattie <beattie@aracnet.com> Cc: Michael Bacarella <mbac@bsd4.nyct.net>, Julian Elischer <julian@elischer.org>, David Scheidt <dscheidt@enteract.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Copy-on-write filesystem Message-ID: <200003032252.OAA02107@mass.cdrom.com> In-Reply-To: Your message of "Fri, 03 Mar 2000 14:49:48 PST." <Pine.LNX.4.21.0003031447050.22409-100000@shell1.aracnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003032252.OAA02107>