Hirdetés
- IDC: 2025-ben a Huawei megnyerte Kínát, az Apple a világot
- Poco F8 Ultra – forrónaci
- Nem engedi el a 128 GB-ot a Google
- Apple iPhone 17 Pro Max – fennsík
- Samsung Galaxy S24 Ultra - ha működik, ne változtass!
- Poco X6 Pro - ötös alá
- iPhone topik
- Huawei P30 Pro - teletalálat
- Meglepően lassú az iOS 26 terjedése
- Samsung Galaxy S25 Ultra - titán keret, acélos teljesítmény
Ú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
- Projektor topic
- Milyen légkondit a lakásba?
- Kerékpárosok, bringások ide!
- IDC: 2025-ben a Huawei megnyerte Kínát, az Apple a világot
- Bluetooth hangszórók
- Gumi és felni topik
- Formula-1
- eldiablo: 30 év után szakítottunk, de azért még beszélünk...
- Suzuki topik
- NVIDIA GeForce RTX 5070 / 5070 Ti (GB205 / 203)
- További aktív témák...
- HIBÁTLAN iPhone 13 mini 256GB Midnight -1 ÉV GARANCIA - Kártyafüggetlen, MS4078
- Karácsonyi Akció! Apple iMac 19.2 i5-8500 Radeon Pro 560X 4GB 16GB 256GB SSD 21.5" 4K Retina
- Lenovo magyar laptop billentyűzetre van szükséged? Akármelyik verzióban segítünk!
- GYÖNYÖRŰ iPhone 13 mini 256GB Blue -1 ÉV GARANCIA - Kártyafüggetlen, MS3904
- Lenovo X13 Yoga 2in1 Thinkpad WUXGA IPS Touch i5.1135G7 16GB 256GB Intel Iris XE Win11 Pro Garancia
Állásajánlatok
Cég: Laptopműhely Bt.
Város: Budapest
Cég: Laptopszaki Kft.
Város: Budapest


