![]() some parttition manage apps are not even able to see it, etc.Īnother side effect (for Linux people): In practice you can not format as Ext4 a VeraCrypt partition if you try on windows. also BootIce see them as IFS: and not as HD#: or RM#. Such way of working of VeraCrypt (comes from TruCrypt, etc) causes another rare things, like SmartDefrag not able to see and defragment files on it (Piriform Deflagger can, so can be a bad algorithm on SmartDrefrag). To whom belongs the fault? In part to Windows NTFS that do not cache estructure changes, in part to VeraCrypt for not emulating a device. That causes a huge, very huge, slow down if compared with non-encrypted. so VeraCrypt must encrypt a lot of times something that will be putted on the exact same cluster of the disk. so in practice windows is asking VeraCrypt for encrypting the same structure a lot of times (when small files are written) in a short period of time. but modifing the NTFS estructure is done without cache. ![]() ![]() So what happens? Windows writes to the NTFS estructure without write cache, then VeraCrypt do the encryption (yes pipelined) and send the encrypted data to the HDD, then Windows see the device has write cache on so waits a little to write the data. Well, that cache affects only to write operations done on the device, since the device is the physical one, it means for encrypted data written to the HDD, not for un-encrypted data written to the NTFS estructure. Remember if write cache is on, do not unplug without windows informing you can safely eject it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |