public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: xiyou.wangcong@gmail.com, kzak@redhat.com, sandeen@redhat.com,
	mcepl@redhat.com
Cc: util-linux@vger.kernel.org
Subject: [QUESTION] why not break the EOF limit of fallocate
Date: Tue, 04 Dec 2012 14:40:22 +0800	[thread overview]
Message-ID: <50BD9AD6.60109@cn.fujitsu.com> (raw)

Hi, everyone.

I have a question about the punch hole function of fallocate. According to
the manual of fallocate command, the hole that we want to punch should not
exceed the end of the file, so my question is why do we forbid fallocate
punching a hole that past EOF?

As we know, we can pre-allocate some space past EOF by fallocate command.
I think punch-hole of fallocate is the most natural approach to reclaim
that space. Though the manual says truncate command can do the same thing,
it is a bit complex, especially we just want to reclaim the front end of
that space.

I find the code of fallocate command doesn't has this limit(fallocate code
doesn't check the range of hole), so I hope we can remove the limit in the
manual if it is possible.

Thanks
Miao

                 reply	other threads:[~2012-12-04  6:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50BD9AD6.60109@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=kzak@redhat.com \
    --cc=mcepl@redhat.com \
    --cc=sandeen@redhat.com \
    --cc=util-linux@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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