On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer *****************************
**Short answer:** **`fsutil file createnew` does *not* write 93rC>GB of zeroes.**
It finishes instantly because it uses an NTFS metadata trick:
**it sets the file *valid data length* and *end-of-file* in the MFT
without actually writing the data blocks.** NTFS then *logically* treats
the file as containing zeroes, but the disk blocks are not physically written.
This is why creating a 93rC>GB file appears instantaneous.
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer *****************************
**Short answer:** **`fsutil file createnew` does *not* write 93rC>GB of zeroes.**
It finishes instantly because it uses an NTFS metadata trick:
**it sets the file *valid data length* and *end-of-file* in the MFT
without actually writing the data blocks.** NTFS then *logically* treats
the file as containing zeroes, but the disk blocks are not physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing zeroes"
If one then reads the file, how does NTFS know not to read the actual data that is IN those blocks?
On Sun, 9/27/2026 2:56 PM, Alan wrote:
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer *****************************
**Short answer:** **`fsutil file createnew` does *not* write 93rC>GB of zeroes.**
It finishes instantly because it uses an NTFS metadata trick:
**it sets the file *valid data length* and *end-of-file* in the MFT
without actually writing the data blocks.** NTFS then *logically* treats >>> the file as containing zeroes, but the disk blocks are not physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing zeroes"
If one then reads the file, how does NTFS know not to read the actual data that is IN those blocks?
https://superuser.com/questions/1619084/what-does-the-command-fsutil-file-createnew-really-do
"The filesystem may keep two separate pointers - the 'end of file' as well as 'end of
valid data'. This is explicitly how NTFS works in Windows.
You can call SetEndOfFile() (corresponding to Linux ftruncate()) to create a large
file with no data, and the space between "end of valid data" and "end of file" will
automatically return all 0x00 bytes when read.
(Privileged accounts can actually use the SetFileValidData() call to force the OS to
return data that is already on disk, but it's not a commonly used operation.)
"
Paul
On 2026-09-27 12:51, Paul wrote:
On Sun, 9/27/2026 2:56 PM, Alan wrote:
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer *****************************
**Short answer:** **`fsutil file createnew` does *not* write 93rC>GB of zeroes.**
It finishes instantly because it uses an NTFS metadata trick:
**it sets the file *valid data length* and *end-of-file* in the MFT
without actually writing the data blocks.** NTFS then *logically* treats >>>> the file as containing zeroes, but the disk blocks are not physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing zeroes"
If one then reads the file, how does NTFS know not to read the actual data that is IN those blocks?
https://superuser.com/questions/1619084/what-does-the-command-fsutil-file-createnew-really-do
"The filesystem may keep two separate pointers - the 'end of file' as well as 'end of
-a valid data'. This is explicitly how NTFS works in Windows.
-a You can call SetEndOfFile() (corresponding to Linux ftruncate()) to create a large
-a file with no data, and the space between "end of valid data" and "end of file" will
-a automatically return all 0x00 bytes when read.
-a (Privileged accounts can actually use the SetFileValidData() call to force the OS to
-a return data that is already on disk, but it's not a commonly used operation.)
"
-a-a-a Paul
And none of that will protect you if someone does a raw scan of the drive's blocks.
On 2026-09-27 12:51, Paul wrote:f
On Sun, 9/27/2026 2:56 PM, Alan wrote:
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want
etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer
***************************** **Short answer:** **`fsutil file
createnew` does *not* write 93rC>GB of zeroes.** It finishes
instantly because it uses an NTFS metadata trick: **it sets the
file *valid data length* and *end-of-file* in the MFT without
actually writing the data blocks.** NTFS then *logically* treats
the file as containing zeroes, but the disk blocks are not
physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing
zeroes"
If one then reads the file, how does NTFS know not to read the
actual data that is IN those blocks?
https://superuser.com/questions/1619084/what-does-the-command-fsutil-
ile-createnew-really-do
"The filesystem may keep two separate pointers - the 'end of file' as
well as 'end of
valid data'. This is explicitly how NTFS works in Windows.
You can call SetEndOfFile() (corresponding to Linux ftruncate()) to
create a large file with no data, and the space between "end of
valid data" and "end of file" will automatically return all 0x00
bytes when read.
(Privileged accounts can actually use the SetFileValidData() call
to force the OS to return data that is already on disk, but it's
not a commonly used operation.)
"
Paul
And none of that will protect you if someone does a raw scan of the
drive's blocks.
On 27 Sep 2026, Alan <nuh-uh@nope.com> posted some news:119c1q0$1oso7$1@dont-email.me:
On 2026-09-27 12:51, Paul wrote:f
On Sun, 9/27/2026 2:56 PM, Alan wrote:
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want
etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer
***************************** **Short answer:** **`fsutil file
createnew` does *not* write 93rC>GB of zeroes.** It finishes
instantly because it uses an NTFS metadata trick: **it sets the
file *valid data length* and *end-of-file* in the MFT without
actually writing the data blocks.** NTFS then *logically* treats
the file as containing zeroes, but the disk blocks are not
physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing
zeroes"
If one then reads the file, how does NTFS know not to read the
actual data that is IN those blocks?
https://superuser.com/questions/1619084/what-does-the-command-fsutil-
ile-createnew-really-do
"The filesystem may keep two separate pointers - the 'end of file' as
well as 'end of
valid data'. This is explicitly how NTFS works in Windows.
You can call SetEndOfFile() (corresponding to Linux ftruncate()) to
create a large file with no data, and the space between "end of
valid data" and "end of file" will automatically return all 0x00
bytes when read.
(Privileged accounts can actually use the SetFileValidData() call
to force the OS to return data that is already on disk, but it's
not a commonly used operation.)
"
Paul
And none of that will protect you if someone does a raw scan of the
drive's blocks.
That depends if anything was ever there.
On 2026-09-27 21:37, Nomen Nescio wrote:
On 27 Sep 2026, Alan <nuh-uh@nope.com> posted some
news:119c1q0$1oso7$1@dont-email.me:
On 2026-09-27 12:51, Paul wrote:f
On Sun, 9/27/2026 2:56 PM, Alan wrote:
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want
etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer
***************************** **Short answer:** **`fsutil file
createnew` does *not* write 93rC>GB of zeroes.** It finishes
instantly because it uses an NTFS metadata trick: **it sets the
file *valid data length* and *end-of-file* in the MFT without
actually writing the data blocks.** NTFS then *logically* treats
the file as containing zeroes, but the disk blocks are not
physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing
zeroes"
If one then reads the file, how does NTFS know not to read the
actual data that is IN those blocks?
https://superuser.com/questions/1619084/what-does-the-command-fsutil
-
ile-createnew-really-do
"The filesystem may keep two separate pointers - the 'end of file'
as well as 'end of
valid data'. This is explicitly how NTFS works in Windows.
You can call SetEndOfFile() (corresponding to Linux ftruncate())
to create a large file with no data, and the space between "end
of valid data" and "end of file" will automatically return all
0x00 bytes when read.
(Privileged accounts can actually use the SetFileValidData()
call to force the OS to return data that is already on disk, but
it's not a commonly used operation.)
"
Paul
And none of that will protect you if someone does a raw scan of the
drive's blocks.
That depends if anything was ever there.
The whole point of the thread is the assumption that there IS
something there.
On 02 Oct 2026, Alan <nuh-uh@nope.com> posted some news:119q6og$2ot8f$1@dont-email.me:
On 2026-09-27 21:37, Nomen Nescio wrote:
On 27 Sep 2026, Alan <nuh-uh@nope.com> posted some
news:119c1q0$1oso7$1@dont-email.me:
On 2026-09-27 12:51, Paul wrote:f
On Sun, 9/27/2026 2:56 PM, Alan wrote:
On 2026-09-22 11:22, Paul wrote:
On Mon, 9/21/2026 4:12 PM, Nomen Nescio wrote:
Did you ever experiement with this?
fsutil file createnew zeroes.txt 100000000 (Any size you want
etc.)
Creates a file full of zeroes.
*********************** CoPilot Answer
***************************** **Short answer:** **`fsutil file
createnew` does *not* write 93rC>GB of zeroes.** It finishes
instantly because it uses an NTFS metadata trick: **it sets the
file *valid data length* and *end-of-file* in the MFT without
actually writing the data blocks.** NTFS then *logically* treats >>>>>>> the file as containing zeroes, but the disk blocks are not
physically written.
This is why creating a 93rC>GB file appears instantaneous.
How does NTFS "then *logically* treat[] the file as containing
zeroes"
If one then reads the file, how does NTFS know not to read the
actual data that is IN those blocks?
https://superuser.com/questions/1619084/what-does-the-command-fsutil >>>>> -
ile-createnew-really-do
"The filesystem may keep two separate pointers - the 'end of file'
as well as 'end of
valid data'. This is explicitly how NTFS works in Windows.
You can call SetEndOfFile() (corresponding to Linux ftruncate()) >>>>> to create a large file with no data, and the space between "end
of valid data" and "end of file" will automatically return all
0x00 bytes when read.
(Privileged accounts can actually use the SetFileValidData()
call to force the OS to return data that is already on disk, but >>>>> it's not a commonly used operation.)
"
Paul
And none of that will protect you if someone does a raw scan of the
drive's blocks.
That depends if anything was ever there.
The whole point of the thread is the assumption that there IS
something there.
Not between your ears there isn't.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 60:08:00 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,017 |