From: Chris Snook <csnook@redhat.com>
To: Lars Noschinski <lklml@ml.noschinski.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How does ext2 implement sparse files?
Date: Thu, 31 Jan 2008 12:18:08 -0500 [thread overview]
Message-ID: <47A202D0.1090303@redhat.com> (raw)
In-Reply-To: <20080131152823.GA29422@lars.home.noschinski.de>
Lars Noschinski wrote:
>
> Hello!
>
> For an university project, we had to write a toy filesystem (ext2-like),
> for which I would like to implement sparse file support. For this, I
> digged through the ext2 source code; but I could not find the point,
> where ext2 detects holes.
>
> As far as I can see from fs/buffer.c, an hole is a buffer_head which is
> not mapped, but uptodate. But I cannot find a relevant source line,
> where ext2 makes usage of this information.
In ext2 (and most other block filesystems) all files are sparse files.
If you write to an address in the file for which no block is allocated,
the filesystem allocates a block and writes the contents to disk,
regardless of whether that block is at the end of the file (the usual
case of lengthening a non-sparse file), in the middle of the file
(filling in holes in a sparse file), or past the the end of the file
(making a file sparse).
-- Chris
next prev parent reply other threads:[~2008-01-31 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 15:28 How does ext2 implement sparse files? Lars Noschinski
2008-01-31 16:51 ` Lennart Sorensen
2008-01-31 17:18 ` Chris Snook [this message]
2008-01-31 18:14 ` Andi Kleen
2008-02-01 10:34 ` Shuduo Sang
2008-02-01 11:08 ` Eric Dumazet
2008-02-01 11:55 ` Lars Noschinski
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=47A202D0.1090303@redhat.com \
--to=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lklml@ml.noschinski.de \
/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