If you call fallocate() over an existing region with data it shouldn't be wiped with 0s. You can also call fallocate() on a hole (in case file was ftruncate()ed to a large size) and that region should get "allocated" (i.e future write to an fallocated() region should NOT fail with ENOSPC).
BTW, does NetBSD have the equivalent of open_by_handle[_at]() and name_to_handle[_at]() system calls?
On Sat, Nov 16, 2013 at 12:40 PM, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote:
I note that glusterfs-3.5 branch requires fallocate(). That one does not
exist in NetBSD yet. I wonder if it can be emulated in userspace: this
is just about writing zeros to the new size, right?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@xxxxxxxxxx
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
https://lists.nongnu.org/mailman/listinfo/gluster-devel
