Hirdetés
- Melyik hordozható audiolejátszót (DAP, MP3, stb.) vegyem?
- 4K vs 8K – Megéri-e a 8K TV 2026-ban?
- Fejhallgató erősítő és DAC topik
- Intel Core i5 / i7 / i9 "Alder Lake-Raptor Lake/Refresh" (LGA1700)
- Áprilisi hardverpasziánsz
- OLED monitor topic
- Fujifilm X
- Azonnali notebookos kérdések órája
- Kormányok / autós szimulátorok topikja
- Szédületes tempót rejt a OneXPlayer 3 az 1-ben kézi PC-je
Új hozzászólás Aktív témák
-
krealon
veterán
válasz
margithid
#1633
üzenetére
Does a rewritten file on NTFS use the same blocks?
"In general, block allocation is the most expensive operation in filesystems, so filesystems will try quite hard to avoid it, in particular by reusing blocks when possible. This would mean the following:
When overwriting an existing file, the same blocks are reused. New blocks are allocated when the new file data exceeds that of the overwritten files.
When truncating an existing file, all the blocks are released, thus potentially reusable for other file operations. In that case, the new file may allocate new blocks. There is no guarantee that the new file contents will reallocate the same blocks, and, in particular, the old blocks might have been reallocated to other files in the mean time.
However, it depends a lot on the filesystem internals. Log-structured filesystems perform all writes sequentially, throughout the whole partition, so it is pretty much guaranteed, with such a filesystem, that the new file will not overwrite the blocks from the old file. Journaling filesystems may copy the file contents to an extra structure (the "journal") in addition to the actual permanent storage (depending on whether the journaling extends to the file contents, or just the metadata). Some filesystems also use a "phase tree" which can be viewed as a log-structured filesystem, with a tree instead of a list; for these, overwrites may or may not happen.
An important point to consider is that block allocation strategies do not depend only on the filesystem, but also on the implementation. There is no guarantee that Windows XP and Windows 7, for instance, behave similarly on the same NTFS filesystem. One OS version may find it worthwhile to keep around old blocks to "speed up (re)allocation" while another could employ another strategy. This is all heuristics, tuned and retuned. Thus, one cannot really answer your question about "NTFS"; one would have to talk about "NTFS as implemented in OS foobar, version 42.17, build 3891"."
Vagyis a naplozott fajlrendszer miatt, az uj fajlokat, lehetoleg korabban nem hasznalt blokkokra teszi a rendszer, igy a torolt fajlok az disk image-ben tovabbra is foglaljak a helyet. Ezert novekednek folyamatosan a virtualis gep disk-image fajljai.
Új hozzászólás Aktív témák
- Samsung Galaxy S23 Ultra / 8/256GB / Kártyafügetlen / 12Hó Garancia
- Dell XPS 15 9500 - 15,6" hibás kijelző, i7 10750H, 8GB RAM, Nvidia GTX 1650 Ti 4GB VGA
- Shining3D EinScan Pro 2X 3D szkenner
- Bomba ár! HP ProBook 650 G5 - i5-8GEN I 8GB I 256GB SSD I 15,6" FHD I Cam I W11 I Garancia!
- 267 - Lenovo ThinkBook 16 (G6 ABP) - AMD Ryzen 5 7530U, no GPU
Állásajánlatok
Cég: Laptopműhely Bt.
Város: Budapest

