From: David Woodhouse <dwmw2@infradead.org>
To: linux-fsdevel@vger.kernel.org
Subject: File perforation.
Date: Wed, 08 Jan 2003 22:06:00 +0000 [thread overview]
Message-ID: <21551.1042063560@passion.cambridge.redhat.com> (raw)
I keep receiving requests from users to allow space saving by making holes
in files. For people using JFFS2, a compressed file system designed for use
on fairly small solid state storage devices, this is a fairly reasonable
request, and it's also fairly simple to implement. It's only the interface
I'm concerned about.
I've been resisting these requests because I really don't want to do it
with an ioctl on the file. Only if we can have a generic sys_perforate()
would I really want to do it.
Apparently it's hard to implement on block-based file systems. I don't
really care about that though -- just falling back to writing zeroes to the
offending range (or indeed returning -EINVAL) would be perfectly sufficient
until/unless it gets implemented for other file systems. All I want is an
interface that doesn't make me feel dirty :)
Comments?
--
dwmw2
next reply other threads:[~2003-01-08 22:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 22:06 David Woodhouse [this message]
2003-01-08 22:28 ` File perforation Eli Carter
2003-01-08 22:34 ` David Woodhouse
2003-01-08 22:56 ` Eli Carter
2003-01-08 23:14 ` David Woodhouse
2003-01-09 1:22 ` Andrew Morton
2003-01-09 3:23 ` Andreas Dilger
2003-01-08 23:17 ` Steven Whitehouse
2003-01-08 23:16 ` David Woodhouse
2003-01-08 23:36 ` Steven Whitehouse
2003-01-08 23:25 ` David Woodhouse
2003-01-10 1:39 ` Bryan Henderson
2003-01-08 22:45 ` Dave Kleikamp
2003-01-08 22:55 ` Matthew Wilcox
2003-01-08 23:02 ` David Woodhouse
2003-01-11 9:47 ` Christoph Hellwig
2003-01-10 1:34 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 22:24 Steven French
2003-01-11 1:46 ` Bryan Henderson
2003-01-13 3:52 Steven French
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=21551.1042063560@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.