Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All files are damaged after being synchronized with mirror action #8657

Closed
cyberduck opened this issue Mar 12, 2015 · 9 comments
Closed

All files are damaged after being synchronized with mirror action #8657

cyberduck opened this issue Mar 12, 2015 · 9 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 12, 2015

104de78 created the issue

After being synchronized, all files on the website show 0 B. And all original files on my personal computer can not open because they are damaged.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 15, 2015

@dkocher commented

QQ20150307-3.png

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2015

@dkocher commented

~~ I cannot replicate this issue. Please update to the latest release and reopen this issue with exact steps to reproduce. ~~

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2015

@dkocher commented

Regression introduced in a201d50 when local files are moved to Trash and the synchronisation transfer is repeated (possibly with automatic retry due to a network connectivity issue).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2015

@dkocher commented

In de1e556.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 2, 2015

9be51f4 commented

Since this is closed, Trac is probably the wrong place to ask this... But I am currently experiencing this issue on 4.7.

I'm wondering if there might be a way to recover any of the affected files.

Here's what I'm looking at:

  • Action taken: Attempted to sync (down) from a remote ec2 server.
  • Affected data: ~2000 files — code/plaintext and images.
  • Outcome: 3 broken copies of each file; 0 original/working copies.
  • In the following locations:
  1. Remote (orig. source) — each file is either 0 B or 286 B
  2. Local project dir (orig. destination) — each file is 201 KB
  3. ~/.Trash — each file is 201 KB

If there's a better place to ask, please feel free to point me in that direction. Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 14, 2015

@dkocher commented

#9042 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 14, 2015

@dkocher commented

#8993 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 14, 2015

@dkocher commented

Replying to [comment:6 hal9000]:

Since this is closed, Trac is probably the wrong place to ask this... But I am currently experiencing this issue on 4.7.

I'm wondering if there might be a way to recover any of the affected files.

Here's what I'm looking at:

  • Action taken: Attempted to sync (down) from a remote ec2 server.
  • Affected data: ~2000 files — code/plaintext and images.
  • Outcome: 3 broken copies of each file; 0 original/working copies.
  • In the following locations:
  1. Remote (orig. source) — each file is either 0 B or 286 B
  2. Local project dir (orig. destination) — each file is 201 KB
  3. ~/.Trash — each file is 201 KB

If there's a better place to ask, please feel free to point me in that direction. Thanks.

Thanks for the details. We are reopening this issue and hopefully find the issue and a fix. Assign higher priority.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 14, 2015

@dkocher commented

In 18330.

@cyberduck cyberduck closed this Oct 14, 2015
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant