Hi,

The scan on one of my file systems seems to be stuck

  Last filesystem scan:
          status:          running
          start:           2017/07/26 08:29:14 (2d 48min 33s ago)
          last action:     2017/07/26 08:30:37 (2d 47min 10s ago)

The log file repeatedly shows the same file being processed throughout
this period:

  2017/07/28 09:14:14 [5738/1] STATS | ======== General statistics =========
  2017/07/28 09:14:14 [5738/1] STATS | Daemon start time: 2017/07/26 08:29:14
  2017/07/28 09:14:14 [5738/1] STATS | Started modules: scan,policy_run(cleanup)
  2017/07/28 09:14:14 [5738/1] STATS | ======== FS scan statistics =========
  2017/07/28 09:14:14 [5738/1] STATS | current scan interval = 1.0d
  2017/07/28 09:14:14 [5738/1] STATS | scan is running:
  2017/07/28 09:14:14 [5738/1] STATS |      started at : 2017/07/26 08:29:14 
(2.0d ago)
  2017/07/28 09:14:14 [5738/1] STATS |      last action: 2017/07/26 08:30:37 
(2.0d ago)
  2017/07/28 09:14:14 [5738/1] STATS |      progress   : 387679 entries scanned 
(0 errors)
  2017/07/28 09:14:14 [5738/1] STATS |      inst. speed (potential):    490.02 
entries/sec (12.24 ms/entry/thread)
  2017/07/28 09:14:14 [5738/1] STATS |      avg. speed  (effective):      2.21 
entries/sec (1.22 ms/entry/thread)
  2017/07/28 09:14:14 [5738/1] STATS | ==== EntryProcessor Pipeline Stats ===
  2017/07/28 09:14:14 [5738/1] STATS | Idle threads: 0
  2017/07/28 09:14:14 [5738/1] STATS | Id constraints count: 10000 (hash 
min=0/max=6/avg=0.6)
  2017/07/28 09:14:14 [5738/1] STATS | Name constraints count: 10000 (hash 
min=0/max=6/avg=0.6)
  2017/07/28 09:14:14 [5738/1] STATS | Stage              | Wait | Curr | Done 
|     Total | ms/op |
  2017/07/28 09:14:14 [5738/1] STATS |  0: GET_FID        |    0 |    0 |    0 
|         0 |  0.00 |
  2017/07/28 09:14:14 [5738/1] STATS |  1: GET_INFO_DB    | 9438 |    9 |    3 
|    396274 |  1.85 |
  2017/07/28 09:14:14 [5738/1] STATS |  2: GET_INFO_FS    |    0 |    0 |    0 
|    396271 |  0.00 |
  2017/07/28 09:14:14 [5738/1] STATS |  3: PRE_APPLY      |    0 |    0 |    0 
|    396271 |  0.00 |
  2017/07/28 09:14:14 [5738/1] STATS |  4: DB_APPLY       |  379 |  171 |    0 
|    395721 |  0.21 | 100.00% batched (avg batch size: 116.2)
  2017/07/28 09:14:14 [5738/1] STATS |  5: RM_OLD_ENTRIES |    0 |    0 |    0 
|         0 |  0.00 |
  2017/07/28 09:14:14 [5738/1] STATS | DB ops: get=293/ins=1/upd=395720/rm=0
  2017/07/28 09:14:14 [5738/1] STATS | --- Pipeline stage details ---
  2017/07/28 09:14:14 [5738/1] STATS | GET_INFO_DB   : first: 
/home/user01/A/B/run02/wrfV2756-0003-00478-000478-01.hdr, status=processing
  2017/07/28 09:14:14 [5738/1] STATS | GET_INFO_DB   : last: 
/home/user01/A/B/run03/swrafV3158-0004-00623-000623-01.img, status=waiting
  2017/07/28 09:14:14 [5738/1] STATS | DB_APPLY      : first: 
63BBC16B/16033637, status=processing
  2017/07/28 09:14:14 [5738/1] STATS | DB_APPLY      : last: 
63BBC16B/397701125, status=waiting

Restarting mysql hasn't solved the problem.  The scan on my other file
system runs fine.

Any ideas what the problem is and how it can be addressed?

Cheers,

Loris

-- 
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin         Email [email protected]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to