Date: Mon, 6 Mar 2000 13:20:22 +0300 (MSK) From: Andrey Sverdlichenko <blaze@infosec.ru> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Copy-on-write filesystem Message-ID: <Pine.BSF.4.20.0003061317450.1186-100000@blaze> In-Reply-To: <200003032252.OAA02107@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0003061317450.1186-100000>