From: Karel Zak <kzak@redhat.com>
To: Rodrigo Campos <rodrigo@sdfg.com.ar>
Cc: "Pádraig Brady" <P@draigBrady.com>, util-linux@vger.kernel.org
Subject: Re: drill: Make a file sparse without using extra disk space
Date: Fri, 24 Jan 2014 10:34:48 +0100 [thread overview]
Message-ID: <20140124093448.GA24972@x2.net.home> (raw)
In-Reply-To: <20140124021602.GA28658@sdfg.com.ar>
On Fri, Jan 24, 2014 at 02:16:02AM +0000, Rodrigo Campos wrote:
> On Fri, Jan 24, 2014 at 01:00:55AM +0000, Pádraig Brady wrote:
> > On 01/23/2014 09:28 PM, Rodrigo Campos wrote:
> > > I've written a small simple tool to make a file sparse without using extra disk
> > > space, it just digs holes on the file when possible.
Nice idea.
> > > To dig the hole uses the
> > > Linux-specific fallocate(2) syscall with FALLOC_FL_PUNCH_HOLE. So, also, it only
> > > works on some file-systems.
> > >
> > > Do you think that util-linux would be a good place for such a simple, linux-only
> > > program ? The case I see it can be useful is to use on VM images file backed (or
> > > I wrote it with this in mind, at least :)).
> > >
> > This functionality is useful.
> > Would it be possible to just add to fallocate with --punch-hole=sparse or something?
>
> Totally, that's an option too :)
It would be the best way for util-linux, I really don't want to add
another util for fallocate.
Maybe we can use a new option --dig-holes [ --length <size> ] or so.
> > Also dd has the conv=sparse option, so maybe this functionality can be added there.
IMHO would be possible to add this functionality to both places ;-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-01-24 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 21:28 drill: Make a file sparse without using extra disk space Rodrigo Campos
2014-01-24 1:00 ` Pádraig Brady
2014-01-24 2:16 ` Rodrigo Campos
2014-01-24 9:34 ` Karel Zak [this message]
2014-01-24 14:04 ` Rodrigo Campos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140124093448.GA24972@x2.net.home \
--to=kzak@redhat.com \
--cc=P@draigBrady.com \
--cc=rodrigo@sdfg.com.ar \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox