[SQLite DB Corruption testers needed]

Yikes!  I'm behind the curve here.  I updated to 6.7.2 from 6.6.6 a few days ago, before seeing this information.

 

I've not yet had any corruption, but I'm a little worried.   Glancing over this and related threads, so far it seems like only those storing SQLite DBs directly on disk rather than on SSD/Cache are seeing this issue.  Is that correct, or are there reports of people storing appdata on cache with this issue?  

 

Having all my dockers in appdata, and having appdata set to cache only, am I immune to this issue, or should I roll back to 6.6.7?

 

[[6.6.4] No cron job running during the night]

7 minutes ago, bonienl said:

Guys. Lets get this straight.

It is a problem, so thank you for reporting this.

And it needs to get resolved regardless of the priority set to it here.

 

And the reason I answered "not true" is because a properly set up cache will overflow to the array. There is no data loss. It surely is 'inconvenient' that data stays on the cache longer than expected but this is NOT lost data.

 

 

The is a critical enough issue where you really should remove 6.6.4 from the stable release category. 

[[6.6.4] No cron job running during the night]

1 minute ago, bonienl said:

Not true

If you're not running a cache drive mirrored, yet expect data on the cache drive to be flushed to your protected drive pool nightly, but then a week down the line your unprotected cache drive dies, everything you expected to have been flushed to the protected drive pool but wasn't is now lost. 

 

I would call that data loss.

 

[[6.6.4] No cron job running during the night]

Not moving data from cache drive to the drive pool as expected could lead to data loss.

[[6.6.4] No cron job running during the night]

Looks like I'm experiencing the same thing. 

 

I don't understand the downgrade in priority.  I wouldn't call not running mover as scheduled just an "annoyance".  That's a pretty critical piece of caching for most.

 

Guess it's back to 6.6.3....

[6.6.4 Help/Info always expanded by default for every item]

Changed Status to Solved

[6.6.4 Help/Info always expanded by default for every item]

Thanks!  Never noticed that before.  I'm a bit embarrassed.

[6.6.1 - Weekly Parity Check runs daily?]

Looks like it's an issue with Sunday.  Monday seems to generate a more correct cron (though I'm not sure what the "|| :" is trying to do):

 

# Generated parity check schedule:
0 0 * * 1 /usr/local/sbin/mdcmd check  &> /dev/null || :

[6.6.1 - Weekly Parity Check runs daily?]

I'm having the same issue on 6.6.3.  Set to run weekly, but it's running daily.   My 6.5.3 is still running weekly fine.

 

I've tried multiple changes to the scheduler with no luck. 

 

# Generated parity check schedule:
0 0 * * * /usr/local/sbin/mdcmd check  &> /dev/null || :