| |||||||||||||
The two sides of reflink()The two sides of reflink()Posted May 6, 2009 9:22 UTC (Wed) by nix (subscriber, #2304)In reply to: The two sides of reflink() by epa Parent article: The two sides of reflink()
Any userspace that does not expect write() in the middle of a file to
potentially fail with -ENOSPC is broken. Such write()s can fail even now thanks to sparse files. It is true that currently userspace can rely on the second write() in a ftell()/write()/fseek()/write() sequence not failing, but this seems a rather thin thing to rely on, to me.
(Log in to post comments)
The two sides of reflink() Posted May 6, 2009 10:42 UTC (Wed) by epa (subscriber, #39769) [Link]
Thanks for pointing this out. So if currently, creating a 10 gigabyte sparse file does not subtract 10 gigs from your quota nor from the free space report, giving the possibility that writing to the middle of an existing file can run out of space, then making a reflink to a 10 gig file should be treated the same way. There is precedent.
|
|||||||||||||