Re: Copy-on-write filesystem

[Mike Smith]

> > 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,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime.             \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message