From: Andrey Repin <anrdaemon@yandex.ru>
To: Corinna Vinschen via Cygwin <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: Cygwin api to punch a hole into a file?
Date: Mon, 4 Dec 2023 19:07:38 +0300 [thread overview]
Message-ID: <1771266816.20231204190738@yandex.ru> (raw)
In-Reply-To: <ZWm9NNUlxdOunBGP@calimero.vinschen.de>
Greetings, Corinna Vinschen via Cygwin!
> I don't know how Windows stores short files,
By Windows I Think you did mean NTFS.
Then yes, file data for certain short values is stored directly in $MFT.
This is not specifically file contents, and even if a file content is just 1
byte, not necessarily it will be stored in $MFT. It all depends on the entire
size of file metadata. If it does not exceed some-under-1K in total, then file
data may be stored in $MFT as well.
> maybe they are part of the metadata up to a point or some such. However, as
> soon as you raise the size over a given point, the *allocation size* will be
> rounded up to 64K and from that point on, it will be in 64K chunks. Also
> sparsifying and desparsifying of blocks only works in 64K chunks.
--
With best regards,
Andrey Repin
Monday, December 4, 2023 18:56:37
Sorry for my terrible english...
next prev parent reply other threads:[~2023-12-04 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 22:36 Cedric Blancher
2023-11-24 11:01 ` Corinna Vinschen
2023-11-28 10:29 ` Corinna Vinschen
2023-12-01 10:22 ` Cedric Blancher
2023-12-01 11:02 ` Corinna Vinschen
2023-12-04 16:07 ` Andrey Repin [this message]
2023-12-05 6:36 ` Thomas Wolff
2023-12-05 13:53 ` Corinna Vinschen
2023-12-05 14:40 ` Thomas Wolff
2023-12-05 14:47 ` Thomas Wolff
2023-12-05 15:15 ` Corinna Vinschen
2023-12-01 10:44 ` _PC_MIN_HOLE_SIZE pathconf() " Cedric Blancher
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=1771266816.20231204190738@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).