Romex Software Forum

InquiringMind, NTFS does not support out of order writes. What is does support is journaling, which is completely different thing. Windows also supports delayed writes, but they are journaled and in order. What is out of order write? Example: * You do some I/O, and what needs to be written down is i...

@Jaga - i partly agree. I agree data integrity should be 1st. This is why using L2 for defer writes can be still safe. Take bcache as an example. It did it right. On the other hand - we also talked here about L2 read cache, and how crash handles that. Saying that L2 'resets' (I know it's wrong word,...

Please note that L2 verification is only to verify L2 data stored right at the last bootup, not the data stored before the ungraceful shutdown. Here is a detailed explaination for this. https://forum.romexsoftware.com/en-us/viewtopic.php?p=15667#p15667 Wow.. that's.. really odd design! I mean, data...

Are you referring to "write coalescing"? If so, it is a highly useful feature that I have yet to experience problems with. Yes. In normal use it's quite useful feature, I agree. However, problem is in case of sudden power loss. If you write data in order, you can easily recover and discar...

Greatest problem with defer-write is out of order writes. This is what causes greatest issue.
Out of order writes are used to maximize and reduce writes to slow HDD.

Maybe option to disable out of order writes could be added?

Drive (partition) you cache from one OS should not be mounted on other OS.
So, for that partition, go into Disk Management, and remove drive letter so it's not seen.

Using PrimoCache with using dual boot is dangerous and it may/will corrupt your data. Only alternative is to wipe PrimoCache cache on each boot from different OS (it's possible it does that now, not sure, haven't tried actually). Why? Imagine you were running PrimoCache, and majority of stuff you do...

I guess you misunderstood what he meant. Currently, when reading file it's being cached in L1. If file is bigger than L1, parts of it get pushed out (LRU algorithm). L2 cache is populated with that same data LATER, when there is no/low disk activity by reading that same data again from HDD. So whole...

@Jaga: I agree completely with your last post. This is my idea (or should I say request) - to have journaling for L2 when using deferred writes. For L1, ofc, makes no sense - since in case of reboot/power loss you lose L1 content anyway. @Support: I understand this would require some changes. Howeve...

@Jaga: it's quite different - any proper FS, including Windows with NTFS will work differently, or should I say 'properly'. This means that if you flick power button off, there will be loss of data. Depending on type of filesystem you will either have corrupt FS, which you fix with chkdsk/fsck or si...