Romex Software Forum

support wrote: ↑Tue Dec 31, 2019 4:52 pm 1. Verify level-2 cache data on the boot if an ungraceful shutdown happened.

Testing 4.0.0 right now, so far so good - but could you elaborate on this point? What exactly is done when an ungraceful shutdown has happened?

Will you be including the feature in V4 where if you read say 1 Tb of data (as in image processing) and running a 500 Gb SSD drive as L2 cache that it doesn't read ALL of the 1 Tb of data and write it to L2 cache? I think this one is important because one wastes and entire write cycle for the entire drive. Ideally, and I know it is challenging, it would be good in this instance if you "simulate" the L2 write up to the point where the last read data will only populate the L2 cache - even if it does fill it. I just don't want to L2 write the first 500 Gb which will immediately be evicted from cache as the second 500 Gb is written to L2.

There may be another way to approach this but bottom line one shouldn't fill the L2 cache with the same amount of data of the entire SSD that will be immediately replaced in cache. I do go in and turn off L2 for the drive when I am doing a big read like this but it would be nice to not have to think about having to do it and make the program more seamless in this instance. The same might apply if one is copying 1 Tb of data from one drive to another.

I still think this is the most awesome software out there on the planet!! It is so reliable and so functional and flexible with its options.

tyraelmetanamede wrote: ↑Sun Jan 26, 2020 11:38 am

support wrote: ↑Tue Dec 31, 2019 4:52 pm 1. Verify level-2 cache data on the boot if an ungraceful shutdown happened.

Testing 4.0.0 right now, so far so good - but could you elaborate on this point? What exactly is done when an ungraceful shutdown has happened?

In previous versions, after an ungraceful shutdown like sudden power loss or crash, PrimoCache will clear/reset L2 cache contents on boot to avoid the possible conflicts between source data and cached data. Now PrimoCache will verify the cached data. If cached data are identical with source, then PrimoCache will keep cached data. Otherwise, PrimoCache will fetch source data and update cache.

RobF99 wrote: ↑Tue Jan 28, 2020 8:54 am Will you be including the feature in V4 where if you read say 1 Tb of data (as in image processing) and running a 500 Gb SSD drive as L2 cache that it doesn't read ALL of the 1 Tb of data and write it to L2 cache?

Yes, we are working on this. Thank you.

I am using Primocache with storage spaces and v4 works perfectly with ntfs formatted volumes, also L1 to L2 flushing is a great advance.
I wonder if there is any progress concerning refs volumes. Specifically when I purposely crash refs volumes on storage spaces while primocache is still flushing data to the volumes they become raw.
I know that this is a generic issue with refs when data is not properly flushed thus I was wondering if you are working on having better support for refs.

@dtsiapas, yes, we are working on it. Thank you for trying the v4 version!

support wrote: ↑Thu Feb 06, 2020 1:57 am @dtsiapas, yes, we are working on it. Thank you for trying the v4 version!

Thank you! Looking forward for this!

I'm guessing that the Alpha release is going very well. Will you go straight to a final, or will you introduce changes and do another Alpha, or make it a Beta?

We may introduce some changes.

Hi Eric,

what is the biggest supported L2 cache size in 4.x?
We had that 2 TByte limit in the past, and now I see plenty of excessively large U.2 SSDs pop up on ebay, which would do perfectly for large scale L2 caches for very large RAID volumes. Many of those U.2 SSDs are 7.68 TByte in size, so it would be really nice, if we can utilize them in full as L2 cache for e.g. a 256 TByte volume.

I guess I need to set up a test system for 4.x on my side to give it a try.

Cheers
Axel