All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: File perforation.
Date: Wed, 08 Jan 2003 16:28:56 -0600	[thread overview]
Message-ID: <3E1CA628.7000002@inet.com> (raw)
In-Reply-To: 21551.1042063560@passion.cambridge.redhat.com

David Woodhouse wrote:
> 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? 

Could you elaborate on the difference between what you want to do and 
sparse files?

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------


  reply	other threads:[~2003-01-08 22:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 22:06 File perforation David Woodhouse
2003-01-08 22:28 ` Eli Carter [this message]
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=3E1CA628.7000002@inet.com \
    --to=eli.carter@inet.com \
    --cc=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.