Files are removed from server after sync is interrupted and resumed later

Bug #462230 reported by Roman Yepishev
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
In Progress
Critical
Facundo Batista
ubuntuone-client (Ubuntu)
Triaged
Critical
Facundo Batista
Karmic
Triaged
Critical
Facundo Batista

Bug Description

Binary package hint: ubuntuone-client

STR:
1. Filled up UbuntuOne directory on main PC (buzz), 136 Mb of data, several big files (10-40 Mb) and lots of small ones.
2. Set up a VM running latest daily live image of Karmic Koala (u1-vm)
3. Added UbuntuOne client account for u1-vm
4. Started syncing
5. Interrupted sync on u1-vm first with direct syncdaemon process kill, then with u1sdtool --quit
6. Resumed syncing on u1-vm
7. Checked the space used info in web interface, 92.9 MB Used (4.5%)

Desired results: No files should be deleted from server
Actual results: Files are lost and if buzz connects to UbuntuOne, it will have its local copies removed as well.

ProblemType: Bug
.home.rtg..cache.ubuntuone.log.oauth.login.log:
 Starting Ubuntu One client version 1.0.2
 Starting Ubuntu One client version 1.0.2
.home.rtg..cache.ubuntuone.log.syncdaemon.exceptions.log:
 2009-10-27 22:57:06,625 - twisted - ERROR - Traceback (most recent call last):
 2009-10-27 22:57:06,626 - twisted - ERROR - Failure: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
.home.rtg..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = True
 connect = 0
 show_applet = 1
Architecture: i386
Date: Tue Oct 27 22:58:52 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091026.2)
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:1261): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1261): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1318): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1324): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Related branches

Revision history for this message
Roman Yepishev (rye) wrote :
Revision history for this message
Roman Yepishev (rye) wrote :
Revision history for this message
Elliot Murphy (statik) wrote :

Thank you for the bug report! This is clearly a critical problem and we'll start working on this immediately.

Changed in ubuntuone-client (Ubuntu):
status: New → Triaged
assignee: nobody → Facundo Batista (facundo)
importance: Undecided → Critical
Revision history for this message
Roman Yepishev (rye) wrote :

Set log_level to DEBUG for syncdaemon and reproduced the issue again.

Elliot Murphy (statik)
Changed in ubuntuone-client:
assignee: nobody → Facundo Batista (facundo)
Changed in ubuntuone-client:
status: New → Triaged
importance: Undecided → Critical
Elliot Murphy (statik)
Changed in ubuntuone-client (Ubuntu):
importance: Critical → Undecided
Revision history for this message
Facundo Batista (facundo) wrote :

Roman... thanks for your effort and help here... it would be really awesome if we can debug this out... but I'd need your help.

If I check the first log (from #2), I don't see any Unlinks (there're some remove_trash), but this will imply that the Unlink happened previously, and got into other log

If I check the second log (from #4), I can see Unlink's, but as the log is trimmed, it doesn't show where they come from.

Here's the issue with logs: they rotate. Everytime you start the client, and everytime the log is more than 1MB, it rotates.

I see that you can reproduce the issue, and I want to ask you a favour.

Please remove the old logs, reproduce the issue (with log_level in DEBUG), and attach *all* the log files in the directory. If you can reproduce it with just a few files or folders, it would be better, because it will generate less logs.

It would be awesome if you can do that, because it'd be the only way to debug this problem, and I really want this to be fixed.

Thank you very much for your time and help!

(btw, you can reach me also via IRC, in Freenode, in #ubuntuone, if you need more interactive directions or want to ask anything, my username there is facundobatista)

Revision history for this message
Roman Yepishev (rye) wrote :

Sure, here are the complete logs.

Actions performed:
pdfs/ folder with some pdfs is added, synced correctly w/o interrupts to u1-vm.
backgrounds/ folder is added on buzz, u1-vm started syncing immediately. Total size on buzz was ~20Mb.
shutting down syncdaemon on u1-vm with u1sdtool -q and starting it with u1sdtool --wait.
Files are being removed from server, then u1-vm and later buzz is removing some files making 7.9Mb out of 20Mb.

Revision history for this message
Facundo Batista (facundo) wrote :

Roman: I want to thank you deeply about your logs, it made me found the bug that causes this. Remember to buy you a beer if we meet sometime.

I'm working now to fix it!

Revision history for this message
jyk (jykaminski) wrote :

Is there a way to recover the data when the problem indeed occurred?

Changed in ubuntuone-client:
status: Triaged → In Progress
Matt Zimmerman (mdz)
Changed in ubuntuone-client (Ubuntu):
importance: Undecided → Critical
Changed in ubuntuone-client (Ubuntu Karmic):
milestone: none → karmic-updates
Revision history for this message
Elliot Murphy (statik) wrote :

Hi Jeremy (jyk), we've been able to confirm that your files were marked for deletion and no longer appear in the UI, but have not been deleted from the storage pool (final deletion from the storage pool is not immediate). It will take a little bit of time, perhaps a day, but we expect to be able to restore your files.

Revision history for this message
jyk (jykaminski) wrote :

Great!!!!!!!!!!!!!
Many Thanks!!!!!!

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.