search

AnantLabs / big5sync

Automatically exported from code.google.com/p/big5sync
1 stars 0 forks source link

[SystemLogicLayer/CompareAndSync] Path Too Long To Sync / Disk Out Of Space #8

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a folder path with maximum number of character
2. Tag it with another folder
3. Create a file in the new folder.

What is the expected output? What do you see instead?
PathTooLongException

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ericnjf on 27 Feb 2010 at 10:18

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/big5sync/w/edit/KnownIssues09

Original comment by sohyuanc...@gmail.com on 16 Mar 2010 at 7:09

GoogleCodeExporter commented 9 years ago

Original comment by gohkhoon...@gmail.com on 26 Mar 2010 at 4:13

GoogleCodeExporter commented 9 years ago 
As of 1.0, the file/folder with PathTooLongException will simply not be synced, 
and no 
error will be thrown. We will think of a way to let the user know in 2.0.

Original comment by sohyuanc...@gmail.com on 31 Mar 2010 at 8:50

GoogleCodeExporter commented 9 years ago 
same as 1.0 , the file and folder will not be sync.

Original comment by ericnjf on 14 Apr 2010 at 8:21

GoogleCodeExporter commented 9 years ago 
The file will simply not be synced. However, as long as it's renamed, it will 
automatically synchronize over if it is in seamless mode, or if you manually 
start a 
sync in manual mode.

It is also logged, so you can check it in logs. For future versions, we will 
look into 
a non-intrusive way of informing the users of these kind of errors.

Original comment by sohyuanc...@gmail.com on 15 Apr 2010 at 6:43

GoogleCodeExporter commented 9 years ago 
To elaborate:

A path too long exception can happen from in both SystemLogicLayer or 
CompareAndSync. 
In both cases, synchronization will carry on as per normal, simply excluding 
the file 
in question. The metadata may get out of sync as a result, but it does not 
affect the 
program function in any way.

When a disk out of space occurs in CompareAndSync, the synchronization will 
simply 
continue till the end.

For both cases, the user is advised to check the user log for more information.

Original comment by sohyuanc...@gmail.com on 15 Apr 2010 at 12:19

GoogleCodeExporter commented 9 years ago 
Issue 202 has been merged into this issue.

Original comment by sohyuanc...@gmail.com on 15 Apr 2010 at 12:23