From: Carlos Maiolino <cmaiolino@redhat.com>
To: "Bradley C. Kuszmaul" <kuszmaul@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: hole punching in ext4
Date: Tue, 22 Jan 2013 11:38:11 -0500 [thread overview]
Message-ID: <20130122163811.GB6021@localhost.localdomain> (raw)
In-Reply-To: <CAKSyJXdbwtOQi==rPZ3nS72bLb9wd0rrmt8RTNPJMUCph-B1Ow@mail.gmail.com>
Ext4 supports it, and you can use fallocate(2) with flag FALLOC_FL_PUNCH_HOLE to
dealloc space of a specific file (please see `man 2 fallocate` for more info).
You can use `fallocate` cmdline program to test it.
Ex:
fallocate -p -o 1024 -l 4096 <filename>
fallocate is available on ext4 since linux 3.1 afaik
About Enterprise distros, it's usually better to contact the customer support to
get information about availability/supportability of a specific feature.
Cheers
On Tue, Jan 22, 2013 at 09:34:59AM -0500, Bradley C. Kuszmaul wrote:
> Hi,
>
> Do any of the ext file systems support hole punching? If so, do the
> redhat distributions support it? Can someone provide an example of a
> program that punches a hole in a file in an ext4 file system?
>
> -Bradley
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Carlos
prev parent reply other threads:[~2013-01-22 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKSyJXfvTFjGMO2ZZPsnSjc_fnUzfs2oMrYf7UQoPvO0=98FxA@mail.gmail.com>
2013-01-22 14:34 ` hole punching in ext4 Bradley C. Kuszmaul
2013-01-22 15:30 ` Eric Sandeen
2013-01-22 16:20 ` Zheng Liu
2013-01-22 23:50 ` Bradley C. Kuszmaul
2013-01-23 0:03 ` Andreas Dilger
2013-01-23 1:38 ` Eric Sandeen
2013-01-22 16:38 ` Carlos Maiolino [this message]
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=20130122163811.GB6021@localhost.localdomain \
--to=cmaiolino@redhat.com \
--cc=kuszmaul@gmail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).