From: Andreas Wagner <thewand@web.de>
To: linux-ext4@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Two questions on sparse files
Date: Wed, 15 Jan 2025 09:34:06 +0100 [thread overview]
Message-ID: <f20639eaa10eaa327dc9a294164b731215d5212f.camel@web.de> (raw)
Hello,
I have two questions on sparse files:
1. Do they really - as media and Wikipedia suggest - reduce allocated
filesize if the file is sparse?
2. Are the blocks of the file in random order?
Thanks in advance and regards,
Andreas Wagner
next reply other threads:[~2025-01-15 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 8:34 Andreas Wagner [this message]
2025-01-15 11:04 ` Two questions on sparse files Simon Richter
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=f20639eaa10eaa327dc9a294164b731215d5212f.camel@web.de \
--to=thewand@web.de \
--cc=linux-ext4@vger.kernel.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