Scrub triggers Date and Time errors

[Z300M]

Asus F1A75-V Pro

FreeNAS-8.0.4-RELEASE-p3-x64 (11703)

My machine's date and time remained fine for 35 days: the daily run output and security run output came every day at 11:01pm.

The last such "normal" security run output was on 06/16/12 at 11:01pm
The next daily run output had a date/time stamp of 06/17/12 at 4:21am and included the report that the first scrubbing (since reboot) of two pools had started.

Then I got the following:

security run output on 08/16/12 at 11:01pm
daily run output on 08/17/12 at 4:41 am -- scrubbing two pools again

security run output on 11/19/12 at 10:01pm
daily run output on 11/20/12 at 3:01 am -- starting scrub of one pool; skipping the other because scrubbing is already in progress

security run output on 12/07/12 at 10:01 pm
daily run output on 12/07/12 at 10:01 pm -- starting scrub of one pool; skipping the other because it's only been 17 days since the last

security run output on 12/08/12 at 10:01 pm
daily run output on 12/08/12 at 10:01 pm -- skipping scrubbing because its only been 18 days since the last for one pool and 0 days for the other

 

[Z300M]

I reset the time and date manually, and the next regular report at 11:01 pm said it was skipping scrub because the last scrub was at <negative large number I have forgotten>, so yesterday I initiated manual scrubs of both pools. This morning (June 23) I see that the date/time is now reported as

Wed Jul 11 01:09:14 2012

I cannot help but conclude that it is the scrub command (whether initiated automatically or manually) that messes up the date and time. Am I the only one seeing this?

 

[Z300M]

And by the way, notice that every one of those new messages has a time stamp of xx.x1 -- every increment is a multiple of 20 minutes.

 

[Z300M]

Scrub triggers Date and Time errors -- Update

As mentioned previously, I have two ZFS pools. One is on four SATA drives connected to the onboard controller. The other is on four IDE drives connected to an add-in PCI card.

The automatic scrub operations were both occurring at the same time, but now that I have again initiated manual scrub operations on each separately it appears that the date and time go crazy only after scrubbing the pool on the IDE drives. I guess it was time to decommission that wimpy little pool anyway.