Files aren't always synced with other devices

Bug #1270195 reported by Alberto Salvia Novella
130
This bug affects 114 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Invalid
Undecided
roopa
ubuntuone-client (Ubuntu)
Won't Fix
Critical
Unassigned
Nominated for Precise by Aron Xu

Bug Description

****************
HOW TO REPRODUCE
****************

You'll need to have a broken folder to reproduce this (follow instructions in comment 5 to do this)

BY RENAMING THE AFFECTED FOLDER:
1. Computer A has the folder, computer B doesn't.
2. Renamed folder in computer A.
3. Ubuntu One syncs.
4. Computer A has the folder and its components, computer B has the folder without its components.

BY MANUALLY COPYING THE AFFECTED FOLDER:
1. Computer A has the folder, computer B doesn't.
2. Compressed folder in computer A into a external hard drive.
3. Deleted folder in computer A, so no computer has the folder.
4. Extracted folder from external hard drive into computer B.
5. Ubuntu One syncs.
6. Computer B has the folder, computer A doesn't.

******************
EXPECTED BEHAVIOUR
******************

- Interrupted uploads to be retried.
- Synced folders to have the same contents.

**************
REAL BEHAVIOUR
**************

- Interrupted uploads aren't retried.
- Sometimes there appear missing contents in synced folders along different devices.

***********
WORK-AROUND
***********

REMOVE FOLDER IN THE SERVER:
1. Compress the folder affected by this bug; by right-clicking on it and selecting the "compress..." option, and following steps in the screen.
2. Delete the affected folder.
3. In one.ubuntu.com, remove the affected folder.
4. From the compressed file just created; extract its contents where they were initially located, by right-clicking on it and selecting the "uncompress here..." option.
5. Delete the compressed file.

****************
RELEVANT DETAILS
****************

- You can easily test if a folder is affected by comparing its number of elements in different devices (righ-click and "properties").
- After the file in a synced folder it is uploaded ('u1sdtool --current-transfers' has shown that all bytes are sent) but server don't assign a hash ID and web interface show this file as 'uploading'. The GUI on Nautilus mark file as synced.

**************
TECHNICAL INFO
**************

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntuone-client 13.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Jan 17 16:40:10 2014
InstallationDate: Installed on 2013-05-21 (241 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntuone-client
UpgradeStatus: Upgraded to saucy on 2013-10-18 (91 days ago)

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Since this bug can easily cause data corruption and lost , it has a priority of "critical".

Changed in ubuntuone-client (Ubuntu):
importance: Undecided → Critical
tags: added: chicharra i386 precise quantal raring testcase
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntuone-client (Ubuntu):
status: New → Confirmed
dobey (dobey)
tags: removed: raring
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Since this bug is:

- Valid.
- Well described.
- Reported in the upstream bug tracker (Launchpad).
- Ready to be worked on by a developer.

it's also triaged.

Changed in ubuntuone-client (Ubuntu):
status: Confirmed → Triaged
Changed in ubuntuone-client:
status: New → Confirmed
Changed in ubuntuone-fsevents-daemon:
status: New → Confirmed
Changed in ubuntuone-fsevents-daemon:
status: Confirmed → New
Changed in ubuntuone-client:
status: Confirmed → New
dobey (dobey)
no longer affects: ubuntuone-fsevents-daemon
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

HOW TO BREAK FILE SYNCHRONIZATION:
1. Initialize session in three different computers which session is synchronized using Ubuntu One.
1. Create a folder (unsynchronized) full of files (which never had being synced by Ubuntu One, and from different sizes). It has to contain over 30 MB of data.
2. Copy the new folder to a synchronized one.
3. Start to rapidly moving files over synchronized folders (also in a out of the new one created).
4. After a while, let computers finish synchronize.

EXPECTED BEHAVIOUR:
- Computers to have the same amount of files.

REAL BEHAVIOUR:
- Computers different from the one where the moving operation has been performed have less files in it.

CONCLUSION:
- Files event couldn't be followed in every case by the Ubuntu One FsEvent Daemon.

RELEVANT DETAILS:
- Computers use Solid State Drives instead of Hard Disk Drives.

summary: - Interrupted files being uploaded are never synced again with other
- devices
+ Files aren't always synced with other devices
description: updated
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Sorry, I should had to comment before marking this bug as affecting the fsevent daemon.

Revision history for this message
dobey (dobey) wrote :

The fsevents daemon is only for Mac OS. Are you verifying that events are not being noticed on Mac OS? If not, it is not affected. And if so, then ubuntuone-client is not affected, because it would be an issue isolated to the fsevents daemon on Mac OS.

no longer affects: ubuntuone-fsevents-daemon
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@Rodney:

Sorry for the mistake, and thanks for the clarification.

roopa (roopat85)
Changed in ubuntuone-client:
assignee: nobody → roopa (roopat85)
Changed in ubuntuone-client (Ubuntu):
assignee: nobody → roopa (roopat85)
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

The Ubuntu One client is no longer active.

Changed in ubuntuone-client:
status: New → Confirmed
Changed in ubuntuone-client (Ubuntu):
status: Triaged → Won't Fix
assignee: roopa (roopat85) → nobody
Changed in ubuntuone-client:
assignee: roopa (roopat85) → nobody
status: Confirmed → Invalid
roopa (roopat85)
Changed in ubuntuone-client:
assignee: nobody → roopa (roopat85)
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.