-
Notifications
You must be signed in to change notification settings - Fork 340
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
Some hubic chunks exist but are not listed #290
Comments
I can reproduce the bug, but not sure if it is the same bug. I'm running the latest version, in which the chunk directory is nested with a nesting level of 1. There is a bug that causes Duplicacy not to go deeper than the first level and therefore all chunks can't be found. If all chunks are in the same directory (which is the default behavior of 2.0.9 or earlier) and only some chunks are missing, then it is a different bug. |
@gilbertchen It may be the same bug. I use my own build that should be >2.0.10. |
Here is the fix: 612f6e2 |
With your fix I still have missing chunks after a backup and a check (this files were already missing before):
Note that I've not tried to delete all revisions and cache to see the result of each HEAD request. An other idea ? |
Can you add some debugging logs here? duplicacy/src/duplicacy_hubicstorage.go Lines 114 to 122 in 50d2e26
For example:
|
I ran a check with your logs:
The 3 missing chunks do not appear except at the end. |
I created about 26K chunks in my test and couldn't reproduce this bug. Can you run
These are the calls to list files on the hubic storage. Can you compare those missing chunks with markers shown in these call? Are missing chunks close to markers or do they happen to be the markers? You can also play with the number of files returned in a call by changing this line: duplicacy/src/duplicacy_hubicclient.go Line 278 in 50d2e26
Another option is to re-initialize the storage with version 2.0.10 and then the chunk directory will become nested. This can significantly reduce the number of files under one directory and hopefully the issue will go away. However, you'll need to re-upload all chunks. |
I had already tried changing I also tried to start listing from the first missing chunk and got 68 more missing chunks (total 71). I (re)tried a HEAD on the first missing chunk and it is still ok (and I also get a correct 404 with a wrong chunk id):
Could it be a permission issue ? (list vs get) |
What is the total number of files under the There is a similar bug on OneDrive that only occurs when there are more than 20K chunks: OneDrive/onedrive-api-docs#740. |
I have 203.372 files in my FYI I get a So what do we do ? I can try a new backup in an other hubic folder... |
Your best bet is to start a new backup. If you use the 2.0.10 version to initialize a new storage directory, the chunks directory will have a nesting level of 1. You can also try using rclone to copy the missing chunk to your local machine to see if they have the same issue. |
I tried rclone but since listing fails to find the chunks I can't do anything. I'm starting a new backup... I hope it will work. I think you can close this issue. This is probably a problem on hubic. |
A fix is to check the existence of each missing chunk individually if they can't be found by the list call. I started to think that this fix is needed now considering both OneDrive and Hubic have the same issue. And you can't rely on them to fix it -- OneDrive/onedrive-api-docs#740 hasn't been updated in 25 days. Of course as you pointed out the snapshot revisions may still not being completely listed, but at least we hope there won't be too many revisions for this bug to appear. |
Same for hubic, I sent an email to the support 40 days ago, no answer... Implementing a HEAD to confirm missing files would be a nice feature. Up to you ! For me it's a nice to have, there are more important issues/features. |
This issue has been mentioned on Duplicacy Forum. There might be relevant details there: |
After a backup and a check of a repository on hubic, I get this kind of result:
It seems that calling an HTTP HEAD on these files returns ok (code 200) but an HTTP GET on the parent directory does not return these files.
I tried several times to delete local cache and remote snapshot, then doing a new backup and check. Each time HTTP HEAD returns ok during backup on the chunks warned by the next check. But there is less and less files warned.
I don't think it's a big issue for chunks (just a small performance issue) but if some snapshot revisions are not correctly listed by duplicacy, some chunks could be considered as not used and then deleted after a prune... with data lost...
Is there a bug in duplicacy ? An issue with hubic (that could be solved in duplicacy with a workaround) ?
The text was updated successfully, but these errors were encountered: