Linux filesystem development
 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:56:16 -0600	[thread overview]
Message-ID: <3E1CAC90.6050303@inet.com> (raw)
In-Reply-To: 22288.1042065284@passion.cambridge.redhat.com

David Woodhouse wrote:
> eli.carter@inet.com said:
> 
>> Could you elaborate on the difference between what you want to do and
>> sparse files?
> 
> 
> 
> No difference. Given a non-sparse file, I want a way to make it sparse.
> 
> Well, I _have_ a way to make it sparse; all I have to do is write out a
> single log entry. What I am lacking is a way for the user to tell me to do
> so :)
> 
> I'm aware that you can do this by deleting the file and writing out a new
> copy. But this is flash and it has a limited number of write cycles; I don't
> want to do that.

(No answers, just questions... ;) )

On a compressed fs like jffs2, wouldn't a block of 0's compress down to 
next-to-nothing already?

Can the fs recognize a big block of 0's and make it sparse on-the-fly 
without needing the user to specify it?  (On block-based fs's, that 
might not always be desirable due to out-of-space errors on modifying a 
file, but for a compressed fs, that's not a new issue.)

(Hmm.... If I'm missing something obvious, clue-by-four me and I'll go 
away. ;) )

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:56 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
2003-01-08 22:34   ` David Woodhouse
2003-01-08 22:56     ` Eli Carter [this message]
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=3E1CAC90.6050303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox