linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Bradley C. Kuszmaul" <kuszmaul@gmail.com>,
	Zheng Liu <gnehzuil.liu@gmail.com>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: hole punching in ext4
Date: Tue, 22 Jan 2013 19:38:38 -0600	[thread overview]
Message-ID: <50FF3F1E.30001@redhat.com> (raw)
In-Reply-To: <59CF9743-8837-4279-9B5A-8AD0878BF5F2@dilger.ca>

On 1/22/13 6:03 PM, Andreas Dilger wrote:
> On 2013-01-22, at 4:50 PM, Bradley C. Kuszmaul wrote:
>> Thanks, this has been a very helpful thread.
>>
>> How do I determine and control whether a file is extent-based?
> 
> You can use "lsattr" on the file, and look for the "e" attribute.
> 
> This should be standard for any ext4-formatted filesystem.  For
> filesystems upgraded from ext3, you need to "tune2fs -O extents"
> to enable this feature.

But since it sounds like you might be on RHEL, don't do that.  We don't
test it or support it.  If you want ext4, mkfs.ext4 the device and go
from there.

-Eric

> Cheers, Andreas
> 
>> On Tue, Jan 22, 2013 at 11:20 AM, Zheng Liu <gnehzuil.liu@gmail.com> wrote:
>>> Ext4 file system supports hole punching.  But until now only extent-based
>>> file supports it.  As far as I know, redhat distributions don't support
>>> hole punching.  You can find a sample program from e2fsprogs which is in
>>> $e2fsprogs/conrib/fallocate.c.  The latest fallocate(1) in util-linux
>>> also can be as a demo.
>> --
>> 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
> 
> --
> 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
> 


  reply	other threads:[~2013-01-23  1:39 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 [this message]
2013-01-22 16:38   ` Carlos Maiolino

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=50FF3F1E.30001@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@dilger.ca \
    --cc=gnehzuil.liu@gmail.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).