Re: Copy-on-write filesystem

[Andrey Sverdlichenko]

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message