Struck on "gathering changes"

Hello

We title says it all. For some reason for the past few days QRecall remains stuck on "gathering changes". No error reported, just nothing backed up...

Logs don't say much:

(that's me canceling after 7h)

The archive passes integrity test.
The mac disk doesn't have any error reported by disk first aid

This is Mac os 10.10.5

Alexandre Takacs wrote:(that's me canceling after 7h)

You have a lot more patience than I do.

The "Locating changes" phase is playing back the filesystem event log to determine what folders contain changes. QRecall requests a playback of changes and then waits to receive them. This should take, at most, a minute, and usually only takes a few seconds.

I suspect something is wrong and OS X simply failed, or started and never finished, sending the events and QRecall was left waiting forever.

This might be a transient problem. First, try restarting your system and try again.

If it happens again, you might consider resetting your filesystem history on Macintosh HD. There's an official API for doing this programmatically, but I don't know of any utilities you can download that will do that for you.

The "unsupported" method is simply wipe the filesystem history for your volume and restart your system. Open up a Terminal window and execute the following command:

The command will prompt you for your admin password. After it finishes, immediately restart your system.

Be very careful about entering this command exactly as shown. The sudo rm command can do some serious damage if incorrectly used.

One of those should fix your problem. If it doesn't, I suspect a deeper issue with OS X.

Hmm

Not sure what to make of this

but

AGTMBP13:/ alex$ ls -la
total 117
drwxr-xr-x   40 root   wheel   1428 19 déc 10:51 .
drwxr-xr-x   40 root   wheel   1428 19 déc 10:51 ..
-rw-rw-r--@   1 root   admin  18436 14 déc 19:08 .DS_Store
d--x--x--x    9 root   wheel    306 19 déc 10:51 .DocumentRevisions-V100
drwx------    2 alex   staff     68  4 déc  2014 .IABootFiles
-rw-r--r--    1 root   wheel    305  4 déc  2014 .IAProductInfo
-rw-r--r--    1 root   wheel    774  5 oct 18:22 .OSInstallerMessages
drwxr-xr-x    2 root   wheel     68  9 oct  2014 .PKInstallSandboxManager
drwx------    5 root   wheel    170  8 oct 21:06 .Spotlight-V100
d-wx-wx-wt    2 root   wheel     68  8 oct 11:33 .Trashes
-rw-r--r--    1 root   wheel    312  2 avr  2014 .apdisk
srwxrwxrwx    1 root   wheel      0 19 déc 10:51 .dbfseventsd
----------    1 root   admin      0  9 sep  2014 .file
drwx------    3 root   wheel    102 19 déc 10:50 .fseventsd
drwx------    4 root   wheel    136 22 jan  2014 .gnupg
drwxr-xr-x@   2 root   wheel     68 10 sep  2014 .vol
drwxrwxr-x+ 209 root   admin   7106 18 déc 12:09 Applications
drwxr-xr-x+  78 root   wheel   2652 24 oct 13:07 Library
drwxr-xr-x@   2 root   wheel     68  9 sep  2014 Network
-rw-r--r--@   1 alex   staff      0 13 mai  2014 OpenFolderListDF?
drwxr-xr-x+   5 root   wheel    170  6 oct 03:00 System
drwxr-xr-x    6 root   admin    204  6 oct 02:59 Users
drwx---rwx@   7 admin  wheel    238 20 nov 00:54 Virtual Machines
drwxrwxrwt@   5 root   admin    170 19 déc 10:51 Volumes
drwxr-xr-x@  39 root   wheel   1326  6 oct 15:19 bin
drwxrwxr-t@   2 root   admin     68  9 sep  2014 cores
dr-xr-xr-x    3 root   wheel   4377 19 déc 10:50 dev
lrwxr-xr-x@   1 root   wheel     11  5 oct 18:13 etc -> private/etc
dr-xr-xr-x    2 root   wheel      1 19 déc 10:51 home
-rw-r--r--@   1 root   wheel    313  1 oct  2014 installer.failurerequests
dr-xr-xr-x    2 root   wheel      1 19 déc 10:51 net
drwxr-xr-x@   2 alex   admin     68 20 déc  2011 nfs
drwxr-xr-x@   6 admin  staff    204  8 aoû  2014 opt
drwxr-xr-x@  10 root   wheel    340  8 oct 15:21 private
drwxr-xr-x@  61 root   wheel   2074  7 oct 00:04 sbin
lrwxr-xr-x@   1 root   wheel     11  5 oct 18:13 tmp -> private/tmp
drwxr-xr-x@  14 root   wheel    476 24 oct 13:07 usr
lrwxr-xr-x@   1 root   wheel     11  5 oct 18:13 var -> private/var

My bad.

I was trying to give you a "safer" command to use, but failed shell expansion rules 101.

Here's the command:

Please don't mistype this one; one errant space and you could wipe your entire drive.

Ok that worked ... and solved the issue !

Thanks !