grive randomly moving local files to .trash with message "change stamp = -1"

Bug #1413737 reported by Paulo Marcel Coelho Aragão
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grive (Ubuntu)
New
Undecided
Unassigned

Bug Description

grive is randomly moving local files to ~/Google Drive/.trash which have not been deleted from Google Drive, with a message like this for each one:

file "./flickr/Adriana Calcanhoto - Tema de Alice.mp3" change stamp = -1
file "./flickr/Adriana Calcanhoto - Tema de Alice.mp3" is deleted in local

Further down the log, I can see that grive then deletes them from Google Drive, with messages like this for each one:

sync "./flickr/Adriana Calcanhoto - Tema de Alice.mp3" deleted in local. deleting remote
HTTP GET "https://docs.google.com/feeds/default/private/full/file%3A0B6eQjhXV-AquV21aVDVaNzJmUDA"
HTTP response 200
HTTP DELETE "https://docs.google.com/feeds/default/private/full/file%3A0B6eQjhXV-AquV21aVDVaNzJmUDA"
HTTP response 200

On this last run, grive deleted 69 files, but on former runs it deleted a different number of files.

I haven't been able to pinpoint which event triggers this, it looks random to me. What is constant is: the files are always deleted from this folder:

drwxrwxr-x 2 paulo paulo 28672 Jan 22 17:33 /home/paulo/Google Drive/flickr

but each time different files are deleted. The files in this folder are static, I haven't changed them, deleted them nor added new files since I started keeping them in Google Drive.

At first I thought Google Drive, for some unknown reason, was itself deleting them. As ~/.grive-last-sync.log is overwritten every time grive runs, I couldn't catch the process on the spot. I had to set up inotify monitoring on ~/Google Drive/.trash, to be alerted whenever any files landed there, so that I could grab a copy of the last ~/.grive-last-sync.log file.

When this happens, I restore the files from Trash on Google Drive, move the local files back from ~/Google Drive/.trash, and run a manual sync just to make sure everything is OK. And it stays OK for an indefinite period, usually not more than one week, when grive suddenly out-of-the-blue deletes another batch of local files from ~/Google Drive/flickr.

What caught my attention was: I had indeed deleted local file ~/Google Drive/modelo declaração diabetes.doc, and grive logged a message exactly like the one logged for the files that were not deleted:

file "./modelo declaração diabetes.doc" change stamp = -1
file "./modelo declaração diabetes.doc" is deleted in local

grive version:

grive 0.3.0-1+git20131016~thefanclub~utopic5
grive-tools 1.12

Please let me know how can I assist in debugging this further.

Revision history for this message
Paulo Marcel Coelho Aragão (marcelpaulo) wrote :
Revision history for this message
Paulo Marcel Coelho Aragão (marcelpaulo) wrote :

Today grive deleted local files again, but not restricted to ~/Google Drive/flickr. I could see that it started deleting local files after this is logged:

Reading remote server file list
HTTP GET "https://docs.google.com/feeds/default/private/full?showfolders=true&showroot=true"
HTTP response 200

I scanned .grive-last-sync.log very closely and noticed references to files which I don't have and never had neither locally nor on Google Drive:

file "Steegle.com - Apps Script - Ad - Postage Stamp" parent doesn't exist, ignored
file "DVDs — R$ 10 cada" parent doesn't exist, ignored

All these symptoms give me the impression that grive somehow and sometimes gets a remote list of files from another Google account which is not mine.

Please let me know how can I assist in debugging this further.

PS: I have attached the .grive-last-sync.log related to this run.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.