- Vezetékes FEJhallgatók
- Apple asztali gépek
- Milyen videókártyát?
- Derekas áremelést jelentett be az ASUS
- Nekimegy saját partnereinek az ARM az AGI CPU-val
- Amlogic S905, S912 processzoros készülékek
- Intel Core i5 / i7 / i9 "Alder Lake-Raptor Lake/Refresh" (LGA1700)
- Idővel a képgenerálást is megkapja a PlayStation
- HTPC (házimozi PC) topik
- Pánik a memóriapiacon
Ú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
- WLAN, WiFi, vezeték nélküli hálózat
- Motorolaj, hajtóműolaj, hűtőfolyadék, adalékok és szűrők topikja
- Vezetékes FEJhallgatók
- Apple iPhone 17e – mágnesek ereje
- eMAG vélemények - tapasztalatok
- Google Pixel topik
- Íme az új Android Auto!
- Folyószámla, bankszámla, bankváltás, külföldi kártyahasználat
- E-roller topik
- Ingatlanos topic!
- További aktív témák...
- 180 - Lenovo LOQ (15IRX9) - Intel Core i7-13650HX, RTX 4060
- Lenovo ThinkPad L16 Gen 1 - 16" WUXGA IPS - Ultra 5 135U - 16GB - 512GB - Win11 - 2 év gari
- ÚJ Magic Keyboard billentyűzetek/ USB-C - Lighning/ 27% Áfás/ Ingyenes szállítás!
- Toshiba KIOXIA XG8 4TB M.2 Gen4 SSD (7,000 MB/s and 5,800 MB/s)
- AKCIÓ! GIGABYTE RTX 5080 AERO OC 16GB videokártya garanciával hibátlan működéssel
Állásajánlatok
Cég: Laptopműhely Bt.
Város: Budapest

