From owner-freebsd-hackers Mon Mar 6 2:18:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pr.infosec.ru (pr.infosec.ru [194.135.141.98]) by hub.freebsd.org (Postfix) with ESMTP id 6A2CE37BD24 for ; Mon, 6 Mar 2000 02:18:44 -0800 (PST) (envelope-from blaze@infosec.ru) Received: from blaze (200.0.0.51 [200.0.0.51]) by pr.infosec.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id D5XL4Z28; Mon, 6 Mar 2000 13:18:11 +0300 Date: Mon, 6 Mar 2000 13:20:22 +0300 (MSK) From: Andrey Sverdlichenko X-Sender: blaze@blaze To: freebsd-hackers@FreeBSD.ORG Subject: Re: Copy-on-write filesystem In-Reply-To: <200003032252.OAA02107@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Mar 2000, Mike Smith wrote: > > 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... It's an application problem, isn't it? Any write() can fail, with EIO, for example. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message