* [QUESTION] why not break the EOF limit of fallocate
@ 2012-12-04 6:40 Miao Xie
0 siblings, 0 replies; only message in thread
From: Miao Xie @ 2012-12-04 6:40 UTC (permalink / raw)
To: xiyou.wangcong, kzak, sandeen, mcepl; +Cc: util-linux
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-12-04 6:40 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-04 6:40 [QUESTION] why not break the EOF limit of fallocate Miao Xie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox