Hole Punch.....<br>That was nice one Greg!!!<br>I would rather try fallocate.<br><br><div class="gmail_quote">On Fri, Aug 5, 2011 at 9:14 PM, Greg Freemyer <span dir="ltr"><<a href="mailto:greg.freemyer@gmail.com">greg.freemyer@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p>Apologies for the top post. I simply forgot to not do that.</p><div><div></div><div class="h5">
<p>On Aug 5, 2011 8:11 AM, "Greg Freemyer" <<a href="mailto:greg.freemyer@gmail.com" target="_blank">greg.freemyer@gmail.com</a>> wrote:<br>
><br>
> There are no "specs" as to how a sparse file is handled in response to writes.<br>
><br>
> Sparse is mostly beneficial when the holes are very large.<br>
><br>
> If an app really wants to have minimal on disk space, you should pre-allocate space with fallocate.<br>
><br>
> You may even need to hole punch after the writes. Both xfs and ext4 support both fallocate and hole punching. (I don't know the userspace call to hole punch. I think its a relatively new feature for ext4.)<br>
><br>
> Greg<br>
><br>
> On Aug 4, 2011 10:16 PM, "Ashish Sangwan" <<a href="mailto:ashishsangwan2@gmail.com" target="_blank">ashishsangwan2@gmail.com</a>> wrote:</p>
</div></div><font color="#888888"><p>Greg </p>
</font></blockquote></div><br>