Author Topic: scheduled update taking extraordinarily long time  (Read 700 times)

Offline wiggum77

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
scheduled update taking extraordinarily long time
« on: August 09, 2014, 08:01:25 pm »
ive been using cruise control snapshot raid for severalyears now, and its been working flawlessly for the most part.

i have an update task scheduled for 245am every morning, and up until yesterday its been working fine as well:

Code: [Select]
[2014-08-08 02:45:00,418] INFO : Trigger update.SilentBobRaid[update][Every Day at: 02:45:00
[Starting = 2013/03/24 00:00:00]
[Ending = null/null/null null:null:null]] fired job SilentBobRaid.SilentBobRaid[update] at:  02:45:00 08/08/2014
[2014-08-08 02:45:00,522] INFO : Executing update...
[2014-08-08 02:45:00,522] INFO : [update] started at: Fri Aug 08 02:45:00 EST 2014
[2014-08-08 02:45:18,040] INFO : Using RAID engine Tx
[2014-08-08 02:48:38,690] INFO : Total process size = 3709861888
[2014-08-08 02:48:38,690] INFO : Max data size = 2921166012416
[2014-08-08 02:48:38,696] INFO : DRU1 size=2909417766912
[2014-08-08 02:48:38,696] INFO : DRU2 size=2921166012416
[2014-08-08 02:48:38,696] INFO : DRU3 size=1176279973888
[2014-08-08 03:02:42,768] WARN : C:\FlexRAID-Managed-Pool\class1_0\{7d4700b2-14b5-48a6-b0a1-eaf8395419c6}\TV - Comedy\Colbert\The.Colbert.Report.2014.08.06.Michael.Fassbender.HDTV.x264-BATV.mp4 no longer exist! Skipping...
[2014-08-08 03:14:15,033] INFO : Successful UPDATE operation!
[2014-08-08 03:14:15,990] INFO : [update] completed at: Fri Aug 08 03:14:15 EST 2014

however yesterday and today, this update operation seems to be takng forever. i had to do a reboot yesterday (for another unrelated issue) and i triggered an update manually, and it took nearly six hours.

and today the scheduled task that was triggerd at 245am appears to be still running, some 8 hours later.



granted, i have recently added several gig of data to the pool over the last day or two, but no more than has been done in the past, and the update tasks has handled this amount of new data before with no issues.

should i be worried? is it possuble one of my drives could have an issue? drive manager indicates they are all healthy

running version 2.0u11 final [Snapshot 1.4 stable / Storage Pool 1.0 RC / Real-Time 1.0 experimental]